In Adobe Experience Manager (AEM), editable templates are a key feature introduced in AEM 6.3 and enhanced in subsequent versions, including AEM as a Cloud Service. These templates allow authors to create and manage page templates dynamically through the Template Editor, unlike static templates that reside under /apps. Editable templates are stored in the CRX repository under the /conf directory, which is the designated location for configuration-related content, including templates and policies.
When a developer creates an editable template, such as home-template in the AEM application wknd, AEM automatically generates a specific node structure in the CRX repository under /conf. The structure follows a standardized hierarchy to store template configurations, policies, and associated metadata. The correct structure for an editable template is as follows:
/conf: The root node for configuration data in AEM, used to store project-specific configurations like editable templates.
wknd [sling:Folder]: A folder node representing the project or tenant (in this case, the wknd application).
settings [sling:Folder]: A subfolder that organizes WCM (Web Content Management) configurations.
wcm [cq:Page]: A node representing the Web Content Management configurations, typically stored as a cq:Page to align with AEM’s page structure.
templates [cq:Page]: A node that holds all editable templates for the project, stored as a cq:Page to allow for template metadata and properties.
home-template [cq:Template]: The actual template node, which is of type cq:Template. This node contains the template’s configuration, including its structure, initial content, and policies.
The node type for the template itself (home-template) is cq:Template, which defines it as an editable template that can be used to create pages. This distinguishes it from a cq:Page node, which is used for actual content pages or structural nodes like the templates parent node. The other options provided in the question are incorrect for the following reasons:
Option A: Incorrectly specifies the home-template node as cq:Page instead of cq:Template. Editable templates are always stored as cq:Template nodes.
Option C: Incorrectly places the structure directly under /wknd without the /conf root, which is not the standard location for editable templates.
Option D: Incorrectly places the structure under /apps, which is used for static templates and application code, not editable templates.
This structure ensures that editable templates are stored in a configuration scope that is separate from application code (/apps) and content (/content), allowing for better management and scalability, especially in multi-tenant environments like AEM as a Cloud Service.
Exact Extracts from Adobe Experience Manager (AEM) Sites Developer Documents:
From "Editable Templates": "Editable templates allow authors to create and maintain templates from the UI. These templates are stored under /conf in the repository, typically in a structure like /conf//settings/wcm/templates/. The template node itself is of type cq:Template."
From "AEM Project Structure": "Editable templates are stored under /conf//settings/wcm/templates. Each template is a cq:Template node, and the parent templates node is a cq:Page. This structure separates configuration data from content and code."
From "Template Editor": "When a template is created via the Template Editor, AEM creates a node structure under /conf//settings/wcm/templates/ with the template node being of type cq:Template, which holds the template’s definition, policies, and initial content."
[Reference: Adobe Experience Manager Sites Developer Documentation, AEM 6.5 and AEM as a Cloud Service, Adobe Experience League., , , ]
