Modeling Content

Design semantic content models by selecting the right canonical model type (Standalone, Collection, Configuration, or Auto-Blocked) for your block's purpose, then structure tables with clear columns and predictable data patterns. This ensures authors can consistently add and manage content without confusion or maintenance overhead.

Standalone models represent single content items, while collection models organize multiple items together. Choose based on whether your block displays one piece of content or groups of related content, ensuring the structure matches how authors think about the data.

Create semantic table structures where each row represents a logical unit and columns have clear, consistent purposes—for example, image, title, and description columns for a card block. This predictability lets authors understand the model immediately and reduces errors.

Yes. Refactor content models by applying semantic integrity principles and compatibility checks with decoration logic. Plan the transition to maintain authoring patterns while conforming to Edge Delivery block structure requirements.

Avoid inconsistent column naming, unclear data purposes, and models that don't match how authors think about content. Use the best practice validation checklist to ensure your model is predictable, reusable, and avoids anti-patterns that create maintenance burden.

Well-designed models reduce author frustration by making content structure intuitive and predictable. This drives consistent content quality, faster authoring, and easier long-term maintenance across your AEM implementation.