content-driven-development

Orchestrate content-first AEM Edge Delivery development with real authored content validation.

1|6|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/aemsites/summit-portal --skill content-driven-development-aemsites
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-driven-development
Source: https://github.com/aemsites/summit-portal/tree/main/skills/aem/edge-delivery-services/content-driven-development
Command: npx skills add https://github.com/aemsites/summit-portal --skill content-driven-development-aemsites

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents coding against assumptions by ensuring AEM Edge Delivery Services changes are developed and validated using real, author-friendly content so regressions and authoring friction are minimized.

Core Features & Use Cases

  • End-to-end CDD workflow: Step-by-step orchestration from starting the dev server to shipping a PR with preview links and validation.
  • Test content strategies: Find existing pages, create local .plain.html drafts, or request CMS content to guarantee coverage of variants and edge cases.
  • Integration with dev checks: Enforces iterative testing, linting, cross-viewport validation, and conventional commit/PR practices for reliable releases.
  • Use case: When adding a new block, design the content model, create accessible test content, implement against that content, run lint/tests, and provide preview links in the PR for reviewers.

Quick Start

Start the CDD workflow by running your dev server, designing or locating test content, implementing changes against that content, validating across viewports, and creating a PR with preview links.

Frequently Asked Questions about content-driven-development

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

FAQPage Schema
How do I validate AEM Edge Delivery Services blocks against real authored content?

Validating AEM Edge Delivery Services blocks against real authored content requires a content-first development workflow that locates or creates test content, runs a local dev server, and iteratively checks browser rendering across viewports before submitting a PR with preview links.

What is content-driven development in AEM and when should I use it?

Content-driven development in AEM is a workflow that ensures code is built and validated using real, author-friendly content. Use it when creating or modifying AEM blocks, applying CSS or JS changes, fixing bugs, or shipping core functionality that requires author validation.

How do I get test content for AEM development when I cannot access the CMS?

When CMS access is unavailable, get test content for AEM development by creating local .plain.html drafts. This local test content guarantees coverage of content variants and edge cases during your development workflow.

Do I need a running local dev server to build AEM Edge Delivery Services features?

Yes, a running local dev server is required to build AEM Edge Delivery Services features using content-driven development. It enables iterative browser validation against your test content before you run linting and create pull requests.

Why does my AEM block code fail when authors enter unexpected content variations?

AEM block code often fails with unexpected content variations because it was coded against assumptions rather than real authored content. Designing a content model and validating against accessible test content minimizes regressions and authoring friction.

What steps are needed to ship an AEM Edge Delivery Services PR with preview links?

Shipping an AEM Edge Delivery Services PR with preview links requires starting your dev server, implementing changes against test content, running lint and tests, validating across viewports, and attaching preview links for reviewers.