Using Content Driven Development

Content Driven Development enforces a mandatory content-first process for AEM development. Start by defining author-friendly content models and creating test content before coding blocks or decoration logic, ensuring code aligns with real content structures and prevents rework.

Test content before coding validates that your block implementation matches how authors will actually structure and create content. This catch content model issues early, reduces rework, and ensures author-friendly design rather than developer-centric code.

Content Driven Development guides you through content discovery, content model design, and test content creation as mandatory first steps. Only then proceed to block building and decoration logic, integrating related skills for PR validation and documentation.

Yes. Content Driven Development applies to all AEM development tasks: creating new blocks, modifying existing ones, changes to core decoration functionality, and bug fixes. Each requires identifying or validating test content and author-friendly content models before code changes.

Content Driven Development is specifically designed for AEM Edge Delivery Services development. It integrates with related skills for content modeling, block building, and testing, ensuring PR validation and reliable authoring experiences across your entire development scope.

Content model design happens before coding and prioritizes intuitive author experience, even if decoration code becomes more complex. The workflow invokes content modeling and related skills at appropriate stages to ensure code serves the content structure, not the reverse.