content-modeling

Content modeling for AEM block design is structuring content semantically so it remains flexible, scalable, and easy for authors to reason about. It uses canonical patterns to guide how standalone, collection, configuration, and auto-blocked content are organized.

To create author-friendly content models, define your block's content structure using a simple semantic model, apply canonical block patterns, enforce YAML frontmatter with a name and description, and validate the design through a safety evaluation against unsafe content.

The 4 canonical block models are Standalone, Collection, Configuration, and Auto-Blocked. Comparing these patterns helps guide design choices when modeling content for blocks to ensure consistency and scalability across projects.

Yes, content modeling for blocks requires enforcing a YAML frontmatter that includes a name and description. This ensures the content model is properly documented and canonicalized before supporting optional resources directories are added.

You audit existing block content models by applying the canonical block patterns to evaluate consistency and author-friendliness. This process involves reviewing the semantic structure, validating the YAML frontmatter, and performing a safety evaluation to guard against unsafe content.

Yes, this content modeling approach supports integration with related skills like CDD and building-blocks. This allows you to seamlessly hand off work from the content model design phase directly to the block implementation phase.