What problem does it solve?
Designing and validating content models for AEM Edge Delivery Services blocks so authors get predictable, semantic, and easy-to-use authoring surfaces that reduce errors and implementation friction.
Core Features & Use Cases
- Canonical pattern guidance: Helps choose between Standalone, Collection, Configuration, and Auto-Blocked models with examples and anti-patterns.
- Structure validation: Provides checklists (maximum cells, semantic formatting, variants vs config cells) and advanced scenarios for nested blocks, per-item config, lists, and forms.
- Documentation output: Specifies the exact model documentation format to return to calling skills or implementers.
- Use case: When building a new card grid or converting ad-hoc lists into a reusable Collection model, follow the steps to produce a predictable, author-friendly model.
Quick Start
Draft a content model for a Cards block where each row represents one item with two columns: image and content (heading, description, CTA).