skills.rest
thojava
thojavaCOMMUNITY
Explore all skills by this author →
GitHub

content-driven-development

Coordinate content-driven development workflows for AEM Edge Delivery Services code changes.

Updated Apr 8, 2026
Search Tags:#workflow#collaboration#validation#content-driven#content-modeling#test-content#aem-edge
One-click install
npx skills add https://github.com/thojava/baco --skill content-driven-development-thojava
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: content-driven-development
Source: https://github.com/thojava/baco/tree/main/.skills/content-driven-development
Command: npx skills add https://github.com/thojava/baco --skill content-driven-development-thojava

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Content Driven Development (CDD) ensures code changes for AEM Edge Delivery Services are validated against real, author-friendly content before coding, reducing risk and rework.

Core Features & Use Cases

  • orchestrates a stepwise workflow from content discovery to ship, ensuring test content is created before coding
  • provides a structured, repeatable process for block creation, decoration changes, and CSS/JS updates across all viewports
  • includes optional resources directories (scripts, references, assets) to support deterministic tasks and documentation

Quick Start

Begin by identifying or creating representative test content and follow the 8-step CDD workflow from planning to ship.

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 validates AEM Edge code changes against real, author-friendly content before coding begins, reducing rework risk by requiring test content creation upfront.

How do I validate AEM Edge block changes against real content?▼

You validate AEM Edge block changes by following a structured 8-step content-driven workflow that coordinates content discovery, test content creation, implementation, linting, and final CMS content preview validation.

Do I need to create test content before coding AEM Edge blocks?▼

Yes, creating representative test content before coding is a strict requirement of the content-driven development workflow, ensuring frontmatter-driven entries and draft PRs capture real CMS content previews.

What's the best way to manage CSS and JS updates across viewports in AEM Edge?▼

The best way is using a content-driven development workflow that provides a repeatable process for decoration changes and CSS/JS updates, validating modifications across all viewports before shipping.

Can I use optional resource directories for deterministic AEM Edge tasks?▼

Yes, the content-driven development workflow supports optional resource directories including scripts, references, and assets to support deterministic tasks and documentation during implementation.

Why does my AEM Edge code fail validation during content-driven development?▼

AEM Edge code validation fails when skipping the structured workflow steps of content modeling, test content creation, or linting, which are required to ensure code matches real content before shipping.

Related Skills

Explore More Content & Communication Skills→
juricamigac-from-hrjuricamigac-from-hr

content-driven-development

Orchestrate a content-first AEM Edge Delivery development workflow with an eight-step validation process.

Official
Advanced
mhaackmhaack

content-driven-development

Coordinate content-first development workflows for AEM Edge Delivery Services tasks.

Community
Advanced
jfoxxjfoxx

content-driven-development

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

Community
Advanced
adobe-summit2026-l613adobe-summit2026-l613

building-blocks

Implement AEM Edge Delivery block changes following content-driven-development patterns.

Official
Advanced