content-modeling

Name: content-modeling
Availability: InStock
Author: valithedge

Apply four canonical content models to design and document block structures.

1|Updated Oct 7, 2024

Search Tags:#documentation #authoring #content-modeling #aem-edge-delivery #canonical-models #block-design

Ready to run

npx skills add https://github.com/valithedge/etisalatedge --skill content-modeling-valithedge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: content-modeling
Source: https://github.com/valithedge/etisalatedge/tree/main/.agents/skills/content-modeling
Command: npx skills add https://github.com/valithedge/etisalatedge --skill content-modeling-valithedge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Content teams often struggle to design consistent, reusable content models for blocks across projects, resulting in brittle implementations and difficult handoffs.

Core Features & Use Cases

Canonical model guidance: Standalone, Collection, Configuration, and Auto-Blocked patterns with best practices.
Structured design process: Steps to understand requirements, design structure, validate against best practices, and document the model.
Real-world examples: Worked examples for blocks like cards, tabs, and embeds to accelerate adoption.

Quick Start

Draft a complete content-model proposal for a new block by selecting a canonical model, outlining the block structure, and listing validation rules.

Frequently Asked Questions about content-modeling

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

FAQPage Schema

How do I create consistent content models for AEM Edge Delivery blocks?▼

To create consistent content models for AEM Edge Delivery blocks, apply the four canonical patterns: Standalone, Collection, Configuration, and Auto-Blocked. This ensures reusable structures, clear validation rules, and streamlined authoring experiences across projects.

What are the four canonical content models for block design?▼

The four canonical content models for block design are Standalone, Collection, Configuration, and Auto-Blocked. They provide structured guidelines to standardize block structure, validation, and documentation, solving issues with brittle implementations and difficult handoffs.

What's the best way to document a block structure for content authors?▼

The best way to document a block structure is to generate a complete content-model specification including the selected canonical model, block structure outline, and validation rules. This provides clear authoring guidelines and reusable patterns for future blocks.

Do I need prior technical knowledge to design content models for documentation?▼

You need a solid understanding of block design requirements and AEM Edge Delivery concepts to design content models effectively. The process requires analyzing requirements, selecting canonical patterns, and defining validation rules to ensure structured documentation.

Why are my content models brittle and hard for authors to use?▼

Content models become brittle and hard to author when teams lack consistent, reusable patterns across projects. Applying canonical models like Standalone and Collection with structured validation rules solves this by ensuring stable, predictable block implementations.

Can I use canonical models for complex blocks like tabs and embeds?▼

Yes, you can apply canonical models to complex blocks like tabs, cards, and embeds. The approach provides real-world worked examples and structured design steps to validate block structure against best practices, accelerating adoption for complex components.