This work allows people with large old prototypes to use the new prototype kit without having to rewrite everything.
On old pages, users would change this line:
{% extends "layout.html" %}
to this:
{% extends "layout-elements.html" %}
This layout is in lib/backward-compatibility along with all the necessary assets and views from version 6 of the kit. When a page is using layout-elements it now uses the old technology - Elements, Frontend toolkit, GOV.UK Template. It does not allow you to use Frontend.
The idea is people can upgrade page by page as needed, and any new pages would use the new technology in Frontend.
Issues:
1. If people have added their own css to app/assets/application.css how do they use that?
I've used the words backward-compatibility, legacy, and elements at various points. We should probably just decide on one, maybe? Possibly two because elements is a well understood concept but not entirely technically accurate - this work provides more than just elements.
This work allows people with large old prototypes to use the new prototype kit without having to rewrite everything.
On old pages, users would change this line:
{% extends "layout.html" %}to this:
{% extends "layout-elements.html" %}This layout is in
lib/backward-compatibilityalong with all the necessary assets and views from version 6 of the kit. When a page is usinglayout-elementsit now uses the old technology - Elements, Frontend toolkit, GOV.UK Template. It does not allow you to use Frontend.The idea is people can upgrade page by page as needed, and any new pages would use the new technology in Frontend.
Issues:
1. If people have added their own css toapp/assets/application.csshow do they use that?backward-compatibility,legacy, andelementsat various points. We should probably just decide on one, maybe? Possibly two becauseelementsis a well understood concept but not entirely technically accurate - this work provides more than just elements.