Using Content Driven Development

Name: Using Content Driven Development
Availability: InStock
Author: pragyap17

Orchestrate AEM Edge Delivery development with content-first requirements and test content modeling.

Updated Sep 18, 2025

Search Tags:#testing #development workflow #author experience #AEM #content modeling #Edge Delivery #content-driven

Ready to run

npx skills add https://github.com/pragyaP17/universal-editor --skill using-content-driven-development-pragyap17

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Developing for AEM Edge Delivery Services without prioritizing content and author needs can lead to inefficient workflows and author-unfriendly content models. This skill enforces a content-first development process to ensure quality and efficiency.

Core Features & Use Cases

Content Discovery & Modeling: Guides identifying existing content or designing new, author-friendly content models.
Test Content Creation: Facilitates creating test content in the CMS or locally, which doubles as PR validation and author documentation.
Orchestrated Implementation: Ensures coding begins only after test content is ready, integrating with other development skills.
Comprehensive Validation: Mandates testing against real content, linting, and PR preparation with accessible test URLs.

Quick Start

Use the 'Using Content Driven Development' skill to start building a new 'Image Gallery' block, beginning with content model design and test content creation.

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 ensure my AEM Edge Delivery blocks prioritize author experience and content models?▼

Content-driven development enforces a content-first process where you design and test content models before coding blocks. Start by discovering existing content or modeling new structures, then create test content in your CMS or locally to validate author workflows and ensure blocks align with how content creators actually work.

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

Test content serves dual purposes: it validates your block implementation against real content structures and acts as PR documentation and author reference. Building test content upfront ensures your block handles the content model correctly and catches design issues before deployment.

What's the right workflow for developing new AEM Edge Delivery blocks?▼

Start with content discovery and modeling to understand author needs, create representative test content, then begin coding only after test content is ready. This orchestrated approach integrates with related skills like content-modeling and testing-blocks to ensure accessible, author-friendly implementations.

Can I use content-driven development for CSS-only styling changes to existing blocks?▼

No, content-driven development applies to all AEM Edge Delivery tasks except trivial CSS-only tweaks. It covers new blocks, block modifications, decoration changes, bug fixes requiring validation, and any code affecting how authors create or structure content.

How does content-driven development integrate with AEM Edge Delivery block testing?▼

The skill orchestrates alignment across related development tasks by mandating test content discovery and modeling before coding, then integrating with testing-blocks and block-collection-and-party skills to ensure comprehensive validation against real content, linting, and PR readiness with accessible test URLs.