Using Content Driven Development

Apply Content Driven Development to AEM Edge Delivery Services tasks.

Updated Apr 14, 2025

Search Tags:#automation #testing #development workflow #authoring #content modeling #aem #cdd

Ready to run

npx skills add https://github.com/amol-anand/demo --skill using-content-driven-development-amol-anand

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Using Content Driven Development
Source: https://github.com/amol-anand/demo/tree/main/.claude/skills/content-driven-development
Command: npx skills add https://github.com/amol-anand/demo --skill using-content-driven-development-amol-anand

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, jsdom, and includes scripts (resource) and references (resource) components.

What problem does it solve?

AEM development often starts with code, leading to author-unfriendly content models, rework, and delayed testing. This Skill enforces a mandatory content-first process, ensuring code is built against real content with author-friendly models.

Core Features & Use Cases

Orchestrated Workflow: Guides you through content discovery, content model design, and test content creation before any coding begins.
Author-Centric Design: Prioritizes intuitive content models, even if it means more complex decoration code, to enhance author experience.
Seamless Integration: Invokes other skills for content modeling, block building, and testing at the appropriate stages.
Use Case: When starting a new "FAQ" block, this skill ensures you first define an author-friendly content model and create test content, preventing costly rework later and providing immediate PR validation.

Quick Start

Initiate the Content Driven Development process for a new 'hero' block.

Frequently Asked Questions about Using Content Driven Development

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

FAQPage Schema

How do I apply content-first development to AEM Edge Delivery Services projects?▼

Content Driven Development enforces a mandatory content-first process for AEM development. Start by defining author-friendly content models and creating test content before coding blocks or decoration logic, ensuring code aligns with real content structures and prevents rework.

Why should I create test content before building AEM blocks?▼

Test content before coding validates that your block implementation matches how authors will actually structure and create content. This catch content model issues early, reduces rework, and ensures author-friendly design rather than developer-centric code.

What's the best workflow for developing new AEM blocks with content validation?▼

Content Driven Development guides you through content discovery, content model design, and test content creation as mandatory first steps. Only then proceed to block building and decoration logic, integrating related skills for PR validation and documentation.

Can I use Content Driven Development for modifying existing AEM blocks and fixing bugs?▼

Yes. Content Driven Development applies to all AEM development tasks: creating new blocks, modifying existing ones, changes to core decoration functionality, and bug fixes. Each requires identifying or validating test content and author-friendly content models before code changes.

Does this approach work with AEM Edge Delivery Services development?▼

Content Driven Development is specifically designed for AEM Edge Delivery Services development. It integrates with related skills for content modeling, block building, and testing, ensuring PR validation and reliable authoring experiences across your entire development scope.

How does content modeling fit into the development workflow?▼

Content model design happens before coding and prioritizes intuitive author experience, even if decoration code becomes more complex. The workflow invokes content modeling and related skills at appropriate stages to ensure code serves the content structure, not the reverse.