Modeling Content

Designing content models for AEM Edge Delivery blocks involves selecting one of four canonical types—Standalone, Collection, Configuration, or Auto-Blocked—based on your block's purpose, then structuring semantic HTML tables that authors can reliably populate without rigid constraints.

Create flexible, semantic table structures with a maximum of four cells per row, using decoration-ready patterns and consistent query selectors across models. This enables predictable authoring and maintains cross-model consistency while minimizing required author input.

Use Standalone models for single-instance content like hero blocks where authors input one set of data. Use Collection models when authors need to compose multiple similar content items together, like a series of tabs or cards.

Apply semantic formatting conventions, maintain consistent cell limits and decoration patterns across canonical model types, and design table structures that enforce predictable authoring workflows, reducing errors and code maintenance burden.

Yes. Migrating blocks to canonical models involves auditing your current table structures, selecting the appropriate model type for each block's purpose, and restructuring to conform to semantic formatting, cell limits, and cross-model consistency requirements.

Auto-Blocked models impose strict structural constraints to enable automatic block detection. Use them only when predictable, machine-parseable row patterns are acceptable; avoid them for blocks requiring flexible or varied row compositions.