content-modeling

Standardize content modeling for author-friendly blocks in AEM Edge Delivery.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/adobe-summit2026-l613/las-vegas-events --skill content-modeling-adobe-summit2026-l613
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-modeling
Source: https://github.com/adobe-summit2026-l613/las-vegas-events/tree/main/.skills/content-modeling
Command: npx skills add https://github.com/adobe-summit2026-l613/las-vegas-events --skill content-modeling-adobe-summit2026-l613

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes content modeling for author-friendly blocks.

Core Features & Use Cases

  • Canonical block models (Standalone, Collection, Configuration, Auto-Blocked)
  • Clear guidance on design, validation, and documentation
  • Anti-patterns, best practices, and practical examples

Quick Start

Create a simple two-column block example and apply one canonical model to illustrate the design.

Frequently Asked Questions about content-modeling

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

FAQPage Schema
What is content modeling for author-friendly blocks in AEM Edge Delivery?

Content modeling for author-friendly blocks standardizes block structures using canonical models like Standalone, Collection, Configuration, and Auto-Blocked to ensure semantic consistency and reuse across projects.

How do I design a content model for a block in AEM Edge Delivery?

Apply canonical models to guide block design by starting with a simple two-column example, validating semantic structure, documenting block patterns, and following best practices to ensure author-friendly reuse.

What are the canonical content models available for AEM Edge Delivery blocks?

The canonical content models for AEM Edge Delivery blocks are Standalone, Collection, Configuration, and Auto-Blocked, each providing standardized structures for specific block design patterns and reuse scenarios.

What are common anti-patterns to avoid when structuring blocks in AEM Edge Delivery?

Common content modeling anti-patterns involve non-semantic structures, poor reuse, and unclear documentation, which are addressed by applying canonical models and following established best practices for block design.

When should I use auto-blocked models over standalone models for content modeling?

Auto-blocked models automate block generation for specific patterns, while Standalone models define independent semantic structures; choosing between them depends on the specific reuse and configuration needs of your block design.