Modeling Content

Content modeling for AEM Edge Delivery blocks involves selecting a canonical model type (Standalone, Collection, Configuration, or Auto-Blocked), structuring table rows and columns semantically, and using decoration code to identify elements like headings, descriptions, and CTAs. This approach ensures authors can create and manage content intuitively without developer intervention.

The four canonical block models are Standalone (single content item), Collection (multiple items in rows), Configuration (settings or metadata), and Auto-Blocked (automatically wrapped content). Select based on whether your block contains one item, many items, configuration settings, or auto-wrapped structures, balancing authoring simplicity with flexibility.

Limit table structures to four cells per row maximum, use semantic formatting (bold or H1 for headings, regular paragraphs for descriptions, links for CTAs), and organize columns so each represents a distinct content element. This prevents author confusion and maintains consistent, maintainable block designs.

Avoid excessive columns, non-semantic content formatting, overly complex nested structures without clear boundaries, and mixing multiple content types in a single row. Poor modeling leads to author frustration, inconsistent content, and difficult maintenance; semantic, well-scoped designs solve these problems.

Yes. Content modeling supports nested blocks and per-item configurations as part of canonical block design. These patterns are handled through decoration code and semantic formatting, allowing complex structures while keeping the authoring interface intuitive and maintainable.

Semantic formatting (H1/bold for headings, paragraphs for descriptions, links for CTAs) enables decoration code to use CSS query selectors to identify and style content elements automatically. This decouples authoring structure from implementation, reducing author burden and keeping block logic clean.