content-modeling

Design semantic content models for AEM Edge Delivery Services blocks.

1|6|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/aemsites/summit-portal --skill content-modeling-aemsites
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-modeling
Source: https://github.com/aemsites/summit-portal/tree/main/skills/aem/edge-delivery-services/content-modeling
Command: npx skills add https://github.com/aemsites/summit-portal --skill content-modeling-aemsites

SYSTEM DOCUMENTATION & REQUIREMENTS

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).

Frequently Asked Questions about content-modeling

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

FAQPage Schema
How do I design author-friendly content models for AEM Edge Delivery Services blocks?

Use canonical model patterns like Standalone, Collection, Configuration, and Auto-Blocked to design author-friendly content models for AEM Edge Delivery Services blocks. This enforces semantic formatting and predictable authoring surfaces.

What are the structural limits for content modeling in AEM Edge Delivery Services?

AEM Edge Delivery Services content modeling enforces a maximum of four cells per row, alongside semantic formatting and variant rules. These constraints ensure block structures remain predictable and reusable for authors.

When should I use a Collection model versus a Configuration model for AEM blocks?

Choose a Collection model for AEM blocks to convert ad-hoc lists into reusable item grids, like cards. Select a Configuration model when defining variant or settings cells to control block behavior without adding content items.

Can I model nested blocks and per-item configurations in AEM Edge Delivery Services?

Yes, AEM Edge Delivery Services content modeling supports advanced scenarios for nested blocks, per-item configurations, lists, and forms. It validates these structures while maintaining semantic formatting and predictable authoring surfaces.

What is the best way to document block structures for AEM Edge Delivery Services implementation?

Document block structures by following the specified model documentation format, outputting clear canonical choices, cell limits, and variant rules. This produces documented block structures ready for AEM Edge Delivery Services implementation.