Content Authoring and Management
What to know
Authoring in AEM revolves around the page editor and its component model. A candidate must distinguish page properties (metadata, thumbnails, vanity URLs, permissions copied to child pages) from component dialog fields, and understand the difference between Edit, Layout, Preview, and Scaffolding modes. Know the role of the parsys / responsive grid, the concept of design dialogs (stored in the design page and controlling allowed components), and templates vs static templates. Understand versions, version comparison, and the Timeline rail (versions, workflows, comments, launches).
Also know MSM basics: live copies, blueprints, rollout configurations, and the difference between inheritance and breaking inheritance. Understand Launches as time-shifted content that is promoted later, and client context/emulators for preview.
Traps
- Questions blur design mode with edit mode: allowed components and design properties belong to the design dialog, not the component dialog.
- "Delete" vs "Deactivate": deleting removes from the repository; deactivating removes from publish.
- Version numbers are not automatically created on every save; they are created manually or via workflow.
- Page properties inheritance: child pages inherit some values only if the field supports it and the child hasn't overridden it.
- Launches are not published directly; they are promoted to the source branch.
Rule of thumb
If a question asks "where do I change which components are available on this page," the answer is the design dialog / template policy, never the component's own dialog.
Worked example: A page shows an outdated hero image; you need to restore a previous version. Open the page, use the Timeline rail, select the earlier version, and choose Revert to this Version - this creates a new version rather than deleting history.