Using Content Driven Development

Enforce a content-first workflow for AEM Edge Delivery Services development.

Updated Feb 15, 2024
One-click install
npx skills add https://github.com/shsteimer/shsteimer-com --skill using-content-driven-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Using Content Driven Development
Source: https://github.com/shsteimer/shsteimer-com/tree/main/.claude/skills/content-driven-development
Command: npx skills add https://github.com/shsteimer/shsteimer-com --skill using-content-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solves? Developers often start coding without clear content models or test content, leading to rework, authoring difficulties, and delayed releases. This skill enforces a content-first development process, ensuring blocks are built against real content and author needs.

Core Features & Use Cases

  • Content-First Workflow: Orchestrates the entire AEM development lifecycle, from content discovery and modeling to implementation and validation, always prioritizing author experience.
  • Automated Content Search: Includes a script to find existing block content on any AEM Edge Delivery host, streamlining testing setup.
  • Use Case: When tasked with building a new "hero" block, this skill guides you to first define the content model, create test content (which can double as author documentation), and then proceed to implementation, ensuring the final block is intuitive for content authors and robustly tested.

Quick Start

Example: Find existing 'hero' block content on localhost

node .claude/skills/content-driven-development/scripts/find-block-content.js hero

Example: Find 'cards' block with 'three-up' variant on a live site

node .claude/skills/content-driven-development/scripts/find-block-content.js cards main--site--owner.aem.live three-up

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 enforce content-first development for AEM blocks?

Content Driven Development enforces a workflow where you discover and model content before coding. Define your content structure, create test content, then build blocks against that real content to ensure author-friendly design and reduce rework.

Can I find existing block content on my AEM Edge Delivery site?

Yes. This skill includes an automated script to search for existing block content across any AEM Edge Delivery host. Run it with a block name to surface test content, streamlining your development setup without manual hunting.

What's the proper workflow for building a new AEM block?

Follow the three-phase process: content discovery and modeling, test content creation, and validation against real content. This ensures blocks are built with author needs in mind and tested against actual content structures before implementation.

When should I use content modeling before block development?

Use content modeling whenever you create or modify blocks, alter decoration functionality, debug issues, or make changes affecting how authors structure content. It's mandatory for all AEM Edge Delivery Services tasks to prevent authoring difficulties and delayed releases.

Why does content-first workflow prevent development delays?

Developers often start coding without clear content models, causing rework and authoring friction. Content Driven Development eliminates this by requiring test content and author validation upfront, ensuring blocks are intuitive and robustly tested before release.

Does this skill work with block variants in AEM?

Yes. The content discovery script supports block variants—search for specific variants like 'three-up' alongside the block name to find relevant test content and understand how authors structure variant-specific content.