Modeling Content

Define canonical content models for author-facing blocks with validation criteria.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/ak8458/abc-boilerplate --skill modeling-content-ak8458
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Modeling Content
Source: https://github.com/ak8458/abc-boilerplate/tree/main/.skills/content-modeling
Command: npx skills add https://github.com/ak8458/abc-boilerplate --skill modeling-content-ak8458

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create semantic, reusable content models for blocks to streamline authorship and ensure consistent rendering across layouts.

Core Features & Use Cases

  • Canonical models: Standalone, Collection, Configuration, Auto-Blocked
  • Table structure and semantic formatting guidelines to keep author input flexible yet predictable
  • Validation and best-practice guidance, with references to resources and integration points with CDD and building-blocks
  • Real-world workflows: designing new blocks, refactoring existing ones, and validating content across projects

Quick Start

Draft a minimal content model example for a Hero block using a Standalone pattern and document the rationale.

Frequently Asked Questions about Modeling Content

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

FAQPage Schema
How do I design content models for AEM edge delivery blocks?

To design content models for AEM edge delivery blocks, define semantic structures and reusable patterns using canonical model types like Standalone, Collection, Configuration, and Auto-Blocked. This ensures author-friendly input and consistent rendering across layouts.

What are canonical model types for structuring blocks?

Canonical model types for structuring blocks include Standalone, Collection, Configuration, and Auto-Blocked patterns. These types categorize content structures to guide semantic formatting, table structures, and validation criteria for author-facing blocks.

When do I need to refactor existing block content structures?

You need to refactor existing block content structures when author input becomes unpredictable or semantic formatting guidelines are not met. Refactoring applies canonical models to validate table structures and ensure reusable patterns across projects.

Does this content modeling approach work with standalone and collection patterns?

Yes, this content modeling approach works with both Standalone and Collection patterns. It specifies table structures, semantic formatting guidelines, and validation criteria across these canonical models to maintain flexible yet predictable author input.

What is the best way to validate content structures across AEM projects?

The best way to validate content structures across AEM projects is to apply the specified canonical model types and validation criteria. This ensures table structures and semantic formatting align with design guidelines for robust, author-friendly blocks.