content-modeling

Document semantic content models for AEM Edge Delivery blocks.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/juricamigac-from-hr/svemojestrane --skill content-modeling-juricamigac-from-hr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-modeling
Source: https://github.com/juricamigac-from-hr/svemojestrane/tree/main/.agents/skills/content-modeling
Command: npx skills add https://github.com/juricamigac-from-hr/svemojestrane --skill content-modeling-juricamigac-from-hr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Content modeling gaps in block authoring are common; this skill helps teams design semantic, reusable content models for AEM Edge Delivery blocks, reducing ambiguity and rework.

Core Features & Use Cases

  • Define and validate content models using the 4 canonical patterns (Standalone, Collection, Configuration, Auto-Blocked).
  • Guide teams from requirements to documentation, ensuring predictable authoring experiences.
  • Apply during block design or changes to existing blocks to align authors and developers on expected structure.

Quick Start

Create a draft content model for a new block using a Standalone or Collection pattern and document it for handoff to downstream skills.

Frequently Asked Questions about content-modeling

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

FAQPage Schema
How do I create semantic content models for AEM Edge Delivery blocks?

To create semantic content models for AEM Edge Delivery blocks, apply canonical patterns like Standalone or Collection, enforce a maximum of four cells per row, and document sections for Block Structure, How It Works, and Key Points to ensure predictable authoring.

What are the canonical content modeling patterns for AEM Edge Delivery?

The canonical content modeling patterns for AEM Edge Delivery are Standalone, Collection, Configuration, and Auto-Blocked. These four patterns define reusable semantic structures to align authors with development teams and reduce ambiguity during block design.

What is the maximum number of cells per row allowed when designing AEM blocks?

The maximum number of cells per row allowed when designing AEM blocks is four. Enforcing this cell limit maintains semantic formatting and predictable authoring experiences within the documented content model.

How do I document content models for AEM block handoff?

Document content models for AEM block handoff by defining the structure using canonical patterns and including dedicated sections for Block Structure, How It Works, and Key Points to align authors and developers on expected content structures.

When should I use canonical patterns for AEM Edge Delivery content modeling?

Use canonical patterns for AEM Edge Delivery content modeling during block design, when reviewing new or updated blocks, and when aligning authors with development teams on expected semantic structures to reduce rework.