Modeling Content

Design and validate AEM Edge Delivery block content models.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/salvamolaso/movistar-poc-aem-eds --skill modeling-content-salvamolaso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Modeling Content
Source: https://github.com/salvamolaso/movistar-poc-aem-eds/tree/main/.skills/content-modeling
Command: npx skills add https://github.com/salvamolaso/movistar-poc-aem-eds --skill modeling-content-salvamolaso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authors often struggle to design robust, reusable content models for blocks, which leads to inconsistent authoring experiences and brittle implementations.

Core Features & Use Cases

  • Guidance to select the appropriate canonical model (Standalone, Collection, Configuration, Auto-Blocked) and to design a flexible table-based structure that supports semantic formatting.
  • Documentation of the content modeling process, including how to validate models against best practices and how to communicate the model to downstream skills (CDD, building-blocks).
  • Real-world examples and a clear Quick Start to bootstrap authoring of block content models.

Quick Start

Design a content model for a Card Grid block with two columns: image and content. Show how authors populate rows and how decoration code will extract elements like the image, title, description, and CTA using semantic markup.

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

Content modeling for AEM blocks involves selecting a canonical pattern (Standalone, Collection, Configuration, or Auto-Blocked), structuring table-based layouts with semantic formatting, and documenting how authors populate rows. This Skill provides guidance on each pattern, real-world examples like Card Grid blocks, and validation against best practices to ensure consistency across authoring experiences.

What's the difference between Standalone, Collection, Configuration, and Auto-Blocked block patterns?

These are four canonical content model patterns for AEM blocks. Each pattern structures how authors input data and how decoration code extracts elements. This Skill covers when to select each pattern, how to design flexible table structures for each, and how semantic markup enables downstream skills to reliably parse block content.

How do I document and validate block content models?

Documentation captures the modeling process, validation rules, and how the model communicates requirements to downstream skills like CDD and building-blocks. This Skill teaches how to validate models against best practices, document authoring workflows, and ensure downstream tools can correctly extract and render block elements.

Can I use semantic formatting to make blocks more reusable?

Yes. Semantic formatting—marking up content with meaningful structure rather than visual markup—makes block models more flexible and reusable. This Skill guides how to apply semantic practices in table-based block structures so decoration code reliably extracts image, title, description, and CTA elements across different block variations.

What problem does a well-designed block content model solve?

A robust content model eliminates inconsistent authoring experiences and brittle implementations by providing authors a clear, structured way to input data and enabling downstream code to reliably parse block elements. This Skill teaches design practices that prevent model fragmentation and ensure blocks scale across your content ecosystem.