Modeling Content

Design canonical content models for AEM Edge Delivery Blocks.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/trieloff/trrrrdt --skill modeling-content-trieloff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Modeling Content
Source: https://github.com/trieloff/trrrrdt/tree/main/.claude/skills/content-modeling
Command: npx skills add https://github.com/trieloff/trrrrdt --skill modeling-content-trieloff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing scalable, author-friendly content models for AEM Edge Delivery blocks so teams can consistently structure block content and reduce rework.

Core Features & Use Cases

  • Guides the design of canonical block models (Standalone, Collection, Configuration, Auto-Blocked) and when to apply them.
  • Provides a structured approach to table-based content modeling that editors can follow across blocks.
  • Real-world examples and decision criteria for validating models and communicating them to downstream skills.

Quick Start

Write a simple, semantic table-based model for a new block, selecting the appropriate canonical model and documenting the rationale for reuse and extension.

Frequently Asked Questions about Modeling Content

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

Canonical block models for AEM Edge Delivery include Standalone, Collection, Configuration, and Auto-Blocked. These models provide structured approaches to table-based content modeling and decision criteria for when to apply each pattern.

How do I structure table-based content for AEM Edge Delivery blocks?

You structure table-based content by writing simple, semantic models that editors can follow across blocks. This involves specifying canonical models, table structures, and validation criteria to ensure predictable, reusable content modeling.

When should I use an Auto-Blocked canonical model instead of a Standalone block?

You use an Auto-Blocked model when content needs automatic block application without manual authoring intervention, whereas Standalone models suit manually authored, independent block content requiring direct editor control.

What validation criteria should I apply when modeling content for AEM blocks?

You should apply validation criteria that ensure consistent semantics across authoring tools and teams. The process involves specifying canonical models, table structures, and documentation formats to reduce rework and guarantee predictable content modeling.

Can I use these content modeling patterns for updating existing AEM Edge Delivery blocks?

Yes, you apply these content modeling patterns to both new blocks and updates. This ensures consistent semantics across authoring tools and teams, reducing rework when modifying existing block structures.