Modeling Content

Design author-friendly content models for AEM Edge Delivery blocks.

Updated Sep 18, 2025
One-click install
npx skills add https://github.com/pragyaP17/universal-editor --skill modeling-content-pragyap17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Modeling Content
Source: https://github.com/pragyaP17/universal-editor/tree/main/.claude/skills/content-modeling
Command: npx skills add https://github.com/pragyaP17/universal-editor --skill modeling-content-pragyap17

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creating intuitive and reusable content structures for AEM Edge Delivery blocks can be complex, leading to authoring difficulties and inconsistent content. This skill guides the design of effective content models that prioritize author experience.

Core Features & Use Cases

  • Canonical Model Selection: Helps choose from Standalone, Collection, Configuration, or Auto-Blocked models based on content needs.
  • Table Structure Design: Guides the creation of flexible, semantic table structures that authors can easily work with in their CMS.
  • Best Practice Validation: Provides a checklist to ensure models are predictable, reusable, and avoid common anti-patterns.
  • Advanced Scenarios: Addresses complex needs like nested blocks, item-level configurations, and list handling.

Quick Start

Use the 'Modeling Content' skill to design a content model for a new 'Hero' block, ensuring it is author-friendly and follows best practices.

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 Edge Delivery blocks?

Design content models by selecting a canonical structure—Standalone, Collection, Configuration, or Auto-Blocked—based on your content needs, then create semantic table structures with a maximum of four cells per row that authors can easily manage in the CMS authoring interface.

What makes a content model author-friendly in AEM?

Author-friendly models prioritize predictable, reusable structures that minimize complexity. Use semantic table designs, avoid anti-patterns, ensure compatibility with decoration code using query selectors, and validate that the model works consistently across all authoring surfaces.

When should I refactor or migrate my AEM content model?

Refactor your content model when creating new blocks, modifying existing blocks that change authoring structure, or when current structures create authoring difficulties or inconsistency. Validation ensures conformance across all CMS authoring surfaces.

How do I handle complex scenarios like nested blocks in content models?

Address nested blocks and item-level configurations by selecting the appropriate canonical model and applying best-practice validation checklists. Ensure semantic structure remains predictable and reusable even as complexity increases.

Can I apply content model best practices across multiple authoring surfaces?

Yes. Design canonical models that work consistently across all CMS authoring surfaces by creating reusable patterns, validating structure conformance, and using semantic table designs that maintain predictability regardless of where authors interact with content.