Site Structure, Navigation, and Templates
What to know
Site structure in AEM is a content tree under /content. Candidates must understand language copies (e.g., /content/site/en, /content/site/fr) and the role of the language navigation component versus breadcrumb and navigation components. Know how root paths and navigation depth properties change what a navigation component displays.
Templates are central. Distinguish editable templates (stored under /conf, composed of structure, initial content, and policies) from static templates (stored in the codebase). Know that editable templates require a template type and that policies map to components. Understand template locking (structure locked vs unlocked) and how initial content differs from structure.
Know client libraries (clientlibs) categories and how templates include them, and the concept of page component inheritance (sling:resourceSuperType).
Traps
- Editable templates live in
/conf, not/apps; static templates live in/apps. - Structure content cannot be edited by authors when locked; initial content can be edited and is copied to new pages.
- Navigation components use a root path relative to the current page unless an absolute path is set.
- Breadcrumb shows the path from the root, not the site map.
- A template type determines which templates can be created under a given path.
Rule of thumb
If a page's layout must be fixed and non-editable, lock the structure; if authors need a starting point they can modify, put components in initial content.
Worked example: Authors report they cannot add a component to the header of new pages. The header is in the template's structure and locked - unlock the structure or move the component to initial content, then republish the template.