Modeling Content

Design content models for AEM Edge Delivery blocks.

Updated Apr 14, 2025
One-click install
npx skills add https://github.com/amol-anand/demo --skill modeling-content-amol-anand
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Modeling Content
Source: https://github.com/amol-anand/demo/tree/main/.claude/skills/content-modeling
Command: npx skills add https://github.com/amol-anand/demo --skill modeling-content-amol-anand

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Poorly designed content models lead to author frustration, inconsistent content, and complex, brittle decoration code. This Skill guides you in creating intuitive, maintainable content structures for AEM blocks.

Core Features & Use Cases

  • Canonical Model Selection: Helps identify the best model type (Standalone, Collection, Configuration, Auto-Blocked) for your block's purpose.
  • Semantic Structure Design: Provides best practices for designing flexible, semantic HTML table structures that are easy for authors to understand.
  • Anti-Pattern Validation: Guides you in validating models against common pitfalls to ensure author-friendliness and long-term maintainability.
  • Use Case: When creating a new "FAQ" block, this skill helps you design an intuitive content model that allows authors to easily add questions and answers without needing to understand complex HTML, making content creation a breeze.

Quick Start

Design a content model for a new 'carousel' block, considering its canonical type.

Frequently Asked Questions about Modeling Content

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a content model for AEM blocks that's easy for authors?

Design content models by selecting the right canonical type (Standalone, Collection, Configuration, or Auto-Blocked) for your block's purpose, then structure semantic HTML tables that authors can intuitively populate without understanding complex markup. This approach reduces author friction and keeps decoration code maintainable.

What are the canonical content model types for AEM Edge Delivery blocks?

AEM Edge Delivery blocks support four canonical models: Standalone (single-purpose blocks), Collection (repeated content groups), Configuration (settings-driven blocks), and Auto-Blocked (automatically generated structures). Choosing the right type ensures your model matches the block's authoring intent and scales predictably.

How do I avoid common content model anti-patterns in AEM?

Validate your model against best practices by ensuring semantic table structure, predictable field organization, and author-friendly naming. Common pitfalls include overly complex nesting, inconsistent field semantics, and decoration-unfriendly patterns that create brittle code and confuse authors.

Can I use this approach when migrating or refactoring existing AEM block models?

Yes. This skill guides content model design for creating new blocks, modifying existing blocks that change authoring structures, and refactoring or migrating models to conform to best practices. It ensures semantic consistency and reusability across migration scenarios.

What's the best way to structure table semantics in AEM content models?

Structure tables with semantic clarity: use consistent column purposes, decoration-friendly patterns that separate content from presentation, and repeatable row schemas that authors understand instantly. Semantic structure reduces downstream decoration complexity and prevents model drift.

Why do poorly designed AEM content models cause problems downstream?

Poorly designed models lead to author frustration, inconsistent content entry, and complex brittle decoration code. Intuitive, maintainable structures prevent these issues by making authoring predictable and keeping presentation logic simple and testable.