Using Content Driven Development

Coordinate content-first development workflows for AEM Edge Delivery projects.

Updated Sep 12, 2025

Search Tags:#automation #workflow #testing #content-driven #content-modeling #block-development #aem-edge

Ready to run

npx skills add https://github.com/ComwrapUkReply/ue-multitenant-root --skill using-content-driven-development-comwrapukreply

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Using Content Driven Development
Source: https://github.com/ComwrapUkReply/ue-multitenant-root/tree/main/.claude/skills/content-driven-development
Command: npx skills add https://github.com/ComwrapUkReply/ue-multitenant-root --skill using-content-driven-development-comwrapukreply

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Content-first development for AEM Edge Delivery projects ensures code is built against real content and author-friendly models, reducing rework and improving PR validation.

Core Features & Use Cases

Orchestrates end-to-end content-driven workflows across discovery, design, implementation, and validation.
Guides creation of test content in CMS or as local HTML to enable realistic testing and author documentation.
Coordinates with related skills (content-modeling, building-blocks, testing-blocks, block-collection-and-party) to speed up development.

Quick Start

Identify a block, create test content in CMS or with local HTML, then invoke the content-modeling, building-blocks, and testing-blocks workflows to validate changes.

Frequently Asked Questions about Using Content Driven Development

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

FAQPage Schema

What is content-driven development for AEM Edge Delivery?▼

Content-driven development for AEM Edge Delivery ensures code is built against real content and author-friendly models. This approach reduces rework and improves PR validation by enforcing phase-driven processes across discovery, modeling, implementation, and validation.

How do I create test content for AEM Edge blocks?▼

To create test content for AEM Edge blocks, you can use the CMS or generate local HTML files. Scripts like find-block-content.js support test content creation and automation to enable realistic testing and author documentation before implementation.

Can I validate AEM Edge block changes using local test content?▼

Yes, you can validate AEM Edge block changes using local test content or CMS content. The workflow coordinates implementation and validation phases by orchestrating related skills like testing-blocks to ensure code is tested against realistic content models.

What is the best way to coordinate content-first workflows for block development?▼

The best way to coordinate content-first workflows for block development is to follow a phase-driven process: identify a block, create test content in the CMS or locally, invoke content-modeling and building-blocks workflows, then validate changes using testing-blocks.

Do I need jsdom to run content-driven development workflows?▼

Yes, jsdom is a required dependency for the content-driven development workflow. It supports the scripts component used to automate test content creation and validate block decoration functionality during the implementation and validation phases.

When should I not use a content-first approach for AEM Edge projects?▼

You should avoid a content-first approach for AEM Edge projects when real content is unavailable or rapidly changing, as the workflow relies on building code against stable content models to reduce rework and ensure accurate PR validation.