Templates are used at various points in AEM:
- When creating a page you need to select a template; this will be used as the base for the new page. The template defines the structure of the resultant page, any initial content and the components that can be used (design properties).
- When creating a Content Fragment you also need to select a template. This template defines the structure, initial elements and variations.
When using a template to create a new page there is no visible difference (to the page author) and no indication of the type of template being used.
- Can be created and edited by your authors.
- Have been introduced to allow you to define the following for any pages created with the template:
- the structure
- the initial content
- content policies
- After the new page is created a dynamic connection is maintained between the page and the template; this means that changes to the template structure will be reflected on any pages created with that template (changes to the initial content will not be reflected).
- Uses content policies (edited from the template editor) to persist the design properties (does not use Design mode within the page editor).
- Are stored under /conf
- See Editable Templates for further information.
- Must be defined and configured by your developers.
- These templates have been available for several versions of AEM.
- A static template is a hierarchy of nodes that has the same structure as the page to be created, but without any actual content.
- Are copied to create the new page, no dynamic connection exists after this.
- Uses Design Mode to persist design properties.
- Are stored under /apps
- See Static Templates for further information.
See Content Fragment Templates for full information.