content-driven-development

Guide AEM Edge Delivery Services development through a content-first CDD workflow.

Updated Mar 27, 2025

Search Tags:#workflow #development process #aem #edge delivery services #content-driven development #cdw

Ready to run

npx skills add https://github.com/jfoxx/residentportal --skill content-driven-development-jfoxx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: content-driven-development
Source: https://github.com/jfoxx/residentportal/tree/main/.skills/content-driven-development
Command: npx skills add https://github.com/jfoxx/residentportal --skill content-driven-development-jfoxx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a Content Driven Development (CDD) workflow, ensuring that all AEM Edge Delivery Services code changes are built against real content, leading to more author-friendly and robust solutions.

Core Features & Use Cases

Content-First Workflow: Prioritizes identifying or creating test content before writing any code.
Structured Development Process: Guides users through a step-by-step process from planning to deployment.
Integrated Tooling: Orchestrates calls to other skills like analyze-and-plan, content-modeling, and building-blocks.
Use Case: When developing a new AEM block, this Skill ensures you first define the content model, create test content, and then build the block to match, preventing rework and improving author experience.

Quick Start

Use the content-driven-development skill to start building a new AEM block by following the defined workflow.

Frequently Asked Questions about 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 is a workflow that mandates identifying or creating real test content before writing any code, ensuring AEM Edge Delivery Services blocks are built against author-friendly content models for robust solutions.

How do I build AEM blocks using a content-first workflow?▼

To build AEM blocks using a content-first workflow, follow a structured process: analyze requirements, define the content model, create test content, implement the code, and then lint, validate, and deploy the changes.

Why should I create test content before implementing AEM Edge Delivery Services code?▼

Creating test content before implementing AEM Edge Delivery Services code ensures your blocks match real data, which prevents rework, improves the author experience, and leads to more validated, robust solutions.

Can I use a content-driven development workflow for my existing AEM blocks?▼

Yes, you can apply the content-driven development workflow to existing AEM blocks by running the process of analysis, content modeling, test content identification, implementation, linting, validation, and deployment.

What is the best way to structure an AEM development process to improve author experience?▼

The best way to structure an AEM development process for better author experience is using content-driven development, which orchestrates test content identification and content modeling before code implementation to prevent rework.