In your Divio Cloud project directories, you will find a
templates directory. This is the place for your project's templates, such as its own base templates.
It's also where you can place templates to override addon applications' templates. Templates at the project level will override templates at the application level if they are on similar paths. This standard Django behaviour, allowing application developers to provide templates that can easily be customised.
For your convenience, when you first create a project, any templates in addons are copied to the project level so you have them right at hand.
For example, templates from Aldryn News & Blog will be copied to
templates/aldryn_newsblog/ in your project.
If a template does not exist in the project's templates directory, Django will simply fall back to the one in the addon itself.
After templates have been copied to the project's
templates directory, they will not be copied again, so as not to overwrite any changes the project developer may have made. However, this does mean that if an addon is subsequently updated and its templates change, those changes will not appear in your project.
In this case:
- if you have made changes to the templates in your project, you will need to obtain any updated templates and merge them with your own versions
- if you have not made any changes, you can simply delete your local versions and Django will use the updated application templates.