AD0-E117 · Question #18
A client is modernizing some of their AEM sites to go from static to editable templates so they can use the latest features around has the following parameters: - The client currently has a dozen…
The correct answer is D. 1. Use the same page components for editable templates. Option D is correct because reusing the existing page components when migrating to editable templates is the least disruptive approach - it preserves the existing parsys-based content on live pages and avoids breaking changes that a new page component would introduce. Since…
Question
A client is modernizing some of their AEM sites to go from static to editable templates so they can use the latest features around has the following parameters:
- The client currently has a dozen static templates that they want to move to editable templates.
- The existing pages use the parsys paragraph system for storing components.
- Each page based on one of the static templates has its own custom properties tab that is unique
for that template type.
- The client wants template authors to be able to create the editable templates.
Which approach should an Architect use to meet these requirements?
Options
- A
- Use a new page component for editable templates based on the core components page
- B
- Use a new page component for editable templates based on the core components page
- C
- Use the same page components for editable templates
- D
- Use the same page components for editable templates
How the community answered
(63 responses)- A21% (13)
- B13% (8)
- C5% (3)
- D62% (39)
Explanation
Option D is correct because reusing the existing page components when migrating to editable templates is the least disruptive approach - it preserves the existing parsys-based content on live pages and avoids breaking changes that a new page component would introduce. Since each static template already has unique custom properties tabs, keeping the same page component allows those dialog configurations to be retained or adapted for editable template page policies without a full rewrite. Template authors can still be empowered to create editable templates independently once the templates are placed under /conf with proper permissions, regardless of whether the underlying page component is new or reused.
Options A and B are wrong because introducing a new page component based on Core Components would require migrating all existing parsys content to responsivegrid, which is a costly content migration that goes far beyond the stated goal of "modernizing templates." Options C and D differ in the secondary steps (not shown in full here), with C likely including an unnecessary or incorrect step - such as replacing parsys with responsivegrid globally - while D takes the pragmatic path of keeping parsys intact for existing content compatibility.
Memory tip: Think "same component, new template location" - migration to editable templates is about moving template definitions to /conf and adding authoring capabilities, not rebuilding your component hierarchy from scratch.
Topics
Community Discussion
No community discussion yet for this question.