A company plans to develop a set of pages with the same design and structure. The only difference between the pages is the content inside the body. What is the belt approach to develop the pages?

Question

Options

• ACreate a specific page template for each page with associated components in each body.
• BUse the out-of-the-box Reference component to allow freedom in content editing.
• CCreate a page template for all pages with a layout container in the body.
• DCreate a page template and put the rich-text editor (RTE) in the body.

• A
  5% (3)
• B
  17% (11)
• C
  71% (47)
• D
  8% (5)

Explanation

Using a single page template with a layout container in the body is the best approach because it enforces a consistent design and structure across all pages through one reusable template, while the layout container acts as a flexible slot that allows unique components and content to be placed per page. This follows the DRY principle - one template governs the shared structure, and content authors fill the body freely on each individual page.

• A is wrong because creating a specific template per page defeats the purpose entirely - you'd have as many templates as pages, making maintenance a nightmare and eliminating reuse.
• B is wrong because the Reference component is designed to reuse existing content from another page, not to enable unique content per page - it actually restricts editorial freedom rather than enabling it.
• D is wrong because locking the body to only an RTE limits authors to rich text; a layout container is strictly more capable, accepting any component type (images, carousels, forms, etc.).

Memory tip: Think "one skeleton, flexible body" - the template is the skeleton (consistent), and the layout container is the body cavity (accepts anything). If the body is a fixed component like an RTE, you've lost flexibility; if you have multiple templates, you've lost reuse.

No community discussion yet for this question.