-
Notifications
You must be signed in to change notification settings - Fork 0
Pages & templates
bartoszWesolowski edited this page Apr 13, 2020
·
10 revisions
- Tools > General > Templates
- editable templates and policies are stored unde
/conf - at root of each site (for example
/content/wknd) you can set acq:allowedTemplatesproperty (available in page properties) to fix which templates should be used for particular page
Main areas:
-
Structure- defines components that are a part of the template. These will not be editable by content authors. Components in this mode might be locked (they can be edited on template only) or unlocked (can be edited on page based on template) -
Initial Content- defines components that the template will start with, these can be edited and/or deleted by content authors -
Policies- defines configurations on how components will behave and what options authors will have available. Policies can be reused in multiple places which minimize configuration duplication.
Enabling template
By default new templates will be in a draft state - this means that author can not use this template yet. After template it's configured it has to be enabled to make it available for authors. To do that open templates view select template do enable, click on ... button and then enable.
Policy are similar to configurations. The advantage of component policy is that we can reuse policy on components that are placed on templates. To open component policy hit the edit policy button
Policy of a layout container contains a configuration that controls which components can be added to this layout (similar mechanism as design configuration in static templates).