Modeling Content

What problem does it solve?

Poorly designed content models lead to author frustration, inconsistent content, and difficult block maintenance. This skill guides you through creating intuitive, semantic, and reusable content models for AEM Edge Delivery blocks, ensuring a smooth authoring experience.

Core Features & Use Cases

• Canonical Model Selection: Helps identify the most appropriate content model type (Standalone, Collection, Configuration, Auto-Blocked) for any block, balancing flexibility with authoring simplicity.
• Best Practices & Anti-Patterns: Provides clear guidelines for designing table structures, using semantic formatting, and avoiding common pitfalls like excessive columns or non-semantic content.
• Use Case: When developing a new "cards" block, this skill helps you define a content model where each card is a row with clear columns for image, heading, and description, making it easy for authors to create and manage card content without needing developer intervention.

Quick Start

Example: A simple Hero block content model

Content Model: Hero

Block Type

Standalone

Table Structure

| Hero | |------| | [Image] | | [Heading, description, and CTA] |

How It Works

Authors create a hero block using a simple table. The structure is flexible:

• Image can be in its own row or column
• Text content (heading, description, CTA) can be together or separated
• Decoration code uses semantic formatting to identify elements:
  • H1 or bold text -> heading
  • Regular paragraphs -> description
  • Links -> call-to-action