e9f8abb659
From Rocky we can now support Django's recursive template inheritance. Let's move away from all these stand alone templates for deployers to override and instead direct them to recursively extend the existing templates and the blocks they need. This adds more blocks, docs on how to use them, and an example theme which can be turned on and used to show how this works. blueprint: less-customization-templates Change-Id: I69f1e16ff1b88cec78580df0911fe3c01b7507dd
26 lines
1.1 KiB
YAML
26 lines
1.1 KiB
YAML
---
|
|
features:
|
|
- |
|
|
With the fixes in Rocky that allow using Django's recursive template
|
|
inheritance we have added new blocks in our ``base.html`` template to allow
|
|
a better means of customizing through your themes. For details see the
|
|
``customizing`` docs.
|
|
deprecations:
|
|
- |
|
|
The customization override templates have been deprecated in favor of using
|
|
recursive inheritance in your themes. The following templates have been
|
|
deprecated and are slated for removal in the U release:
|
|
* ``_footer.html'``
|
|
* ``_login_footer.html``
|
|
* ``_login_form_footer.html``
|
|
* ``horizon/_custom_head_js.html``
|
|
* ``horizon/_custom_meta.html``
|
|
upgrade:
|
|
- |
|
|
To allow certain views to optionally disable analytics tracking when
|
|
handling sensitive data, don't use the ``custom_head_js`` block, or the now
|
|
deprecated template ``horizon/_custom_head_js.html`` for analytics
|
|
tracking. Please read the ``customizing`` docs and instead use the
|
|
dedicated ``custom_analytics`` block so Horizon or its plugins can when
|
|
needed disable tracking on a given view.
|