Updating and managing templates
Versioning: draft vs live
Templates divide material between draft and live. This is distinct from the dev and prod tags used for layouts.
How template updates work
When a published — live — template is updated, the changes are applied instantly to all pages using that template.
There is no need for a manual upgrade or bulk script process. This immediate update model bypasses complex bulk update processes typically associated with components.
Handling unused content
If a template update introduces a new zone rule that disallows a component already in use on a page, that component is moved to an unused content panel when an editor next visits the page.
The editor must then move or delete this content before they can save.
Unused content also appears when you change templates on a page if the new template’s zone rules ban components that were previously allowed.
Read the Changing a template on a page documentation for more information.
Template asset lifecycle
Templates are assets in Squiz Content Management. You can manage template assets using standard CMS operations, such as moving them to the trash or purging them.
Trashing or purging a template asset
This section covers trashing or purging the template asset in Squiz CMS.
To remove a template from a content page, see Removing a template from a page.
When a template asset is moved to the trash or purged in Squiz Content Management System, the front end of published pages remains structurally stable.
The Page Builder communicates directly with a DXP template service. This service stores template information independent of the CMS asset itself.
Decoupling the template information from the CMS increases robustness. If the template asset is moved to the trash or purged, the front end — that is, the published pages — remains structurally stable.
However, when a template asset is moved to the trash or purged, editing access may be locked or warnings provided.