Modeling Content

Creates editable ASTIN-like content models for WordPress blocks.

Updated Aug 26, 2025
One-click install
npx skills add https://github.com/aemysites/sagarsane-20250826 --skill modeling-content-aemysites
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Modeling Content
Source: https://github.com/aemysites/sagarsane-20250826/tree/main/.claude/skills/content-modeling
Command: npx skills add https://github.com/aemysites/sagarsane-20250826 --skill modeling-content-aemysites

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Designing content models that are both flexible for developers and intuitive for authors can be challenging, leading to complex authoring experiences or rigid content structures. This Skill guides you through creating effective content models for AEM Edge Delivery Services blocks.

Core Features & Use Cases

  • Canonical Model Selection: Helps identify the best content model type (Standalone, Collection, Configuration, Auto-Blocked) for your block's purpose.
  • Table Structure Design: Provides guidelines for designing author-facing HTML table structures, emphasizing semantic formatting and flexibility.
  • Best Practice Validation: Offers a checklist to ensure your content models are predictable, reusable, and avoid common anti-patterns.
  • Use Case: When building a new "Cards" block, use this Skill to define a content model where authors can easily add new cards by simply adding rows to a table, with columns for image, title, and description.

Quick Start

Use the Modeling Content skill to design a content model for a new "Hero" block that needs an image, heading, and call-to-action.

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 Services blocks?

Content modeling for AEM Edge Delivery blocks involves selecting a canonical model type (Standalone, Collection, Configuration, or Auto-Blocked), designing semantic HTML table structures for authors, and applying guidelines like semantic headers and four-cell maximum to ensure predictable, reusable content that decoration code can reliably locate.

What's the best way to structure author-facing tables in AEM block content models?

Structure author-facing tables using semantic headers, limit cells to four per row maximum, and map columns to your canonical model type. This ensures consistent structure, enables reliable element location for decoration code, and keeps the authoring experience intuitive while maintaining flexibility for developers.

When should I use Collection versus Standalone content models in AEM blocks?

Use Standalone for single-instance blocks like Hero, and Collection for repeatable blocks like Cards where authors add content by adding rows. Choose based on whether your block needs one structured piece of content or multiple instances, then validate against the four-cell and semantic-header guidelines.

How do I avoid common anti-patterns when modeling content for AEM Edge Delivery blocks?

Validate your content model against best-practice checklists: enforce semantic headers, keep table cells under four per row, ensure columns map clearly to your canonical model, and verify the structure remains reusable across block instances and migrations.

Can I modify an existing content model for an AEM block without breaking decoration code?

Yes, when modifying content models, apply the same semantic table structure and canonical-model mapping rules. Conformance reviews ensure changes maintain predictable layouts so decoration code continues to reliably locate and process content elements.