Using Content Driven Development

Orchestrate AEM Edge Delivery development workflows aligned with real author content.

3|Updated Apr 17, 2025
One-click install
npx skills add https://github.com/arbory-digital-inc/sas-demo --skill using-content-driven-development-arbory-digital-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Using Content Driven Development
Source: https://github.com/arbory-digital-inc/sas-demo/tree/main/.claude/skills/content-driven-development
Command: npx skills add https://github.com/arbory-digital-inc/sas-demo --skill using-content-driven-development-arbory-digital-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Content Driven Development provides a disciplined workflow that ensures AEM Edge Delivery projects are built against real content, aligning authors' needs with technical implementation. It prevents drift between content models and code by requiring staged test content before development proceeds.

Core Features & Use Cases

  • Content-first orchestration: Guides teams through content discovery, modeling, content creation, implementation, and validation.
  • Cross-skill integration: Coordinates with content-modeling, building-blocks, testing-blocks, and block patterns to ensure cohesive delivery.
  • Use Case: When starting a new block, design a test content set first, then implement the block against that content, reducing rework and PR churn.

Quick Start

Follow a three-phase workflow: 1) DISCOVERY: identify available content or design a content model; 2) IMPLEMENTATION: build blocks and decorate against the defined content; 3) VALIDATION: test with real content, run lint/test, prepare PR with test URLs. Use the content-driven prompts to keep projects aligned with author needs.

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 Services?

Content driven development for AEM Edge Delivery is a workflow that aligns technical implementation with real author content by requiring content discovery, modeling, and test content creation before block development begins.

How do I start building an AEM block using content driven development?

Start building an AEM block by following a three-phase workflow: discover and model the content first, implement and decorate the block against that defined content, then validate with real test content before submitting a PR.

Why should I use test content before implementing AEM Edge Delivery blocks?

Using test content before implementing AEM Edge Delivery blocks prevents drift between content models and code, aligns author needs with technical implementation, and reduces rework and PR churn during validation.

Can I integrate content modeling and testing blocks into an AEM development workflow?

Yes, content driven development orchestrates cross-skill integration by coordinating with content-modeling, building-blocks, and testing-blocks to ensure cohesive delivery and validate code against real content models.

Do I need jsdom to validate content driven development for AEM projects?

Yes, jsdom is required as a dependency to run the scripts that validate test content and decorate blocks during the implementation and validation phases of the AEM Edge Delivery workflow.