content-driven-development

To validate AEM Edge Delivery Services code against real content, apply a content-first development workflow orchestrating test content discovery, modeling, and end-to-end validation before implementation. This ensures code changes align with actual author needs.

Content-driven development for AEM is a structured workflow anchoring coding to real content scenarios. It coordinates content discovery, modeling, and validation across blocks and styles to reduce risk and ensure code changes meet actual author requirements.

Start implementing content-driven development for AEM blocks by identifying or creating test content before coding. Follow the structured eight-step process guiding content discovery, modeling, test content creation, implementation, linting, validation, and shipping.

Yes, AEM content-driven development works for bug fixes and decorations. It applies to all AEM development tasks including new blocks, modifications, decorations, bug fixes, and core functionality across the entire content lifecycle.

To set up AEM content-driven development workflows, you need a SKILL.md file containing frontmatter 'name' and 'description'. Optional resource directories for scripts, references, and assets can be included if present in the project.

Validating AEM code changes against real author content before shipping reduces risk by anchoring development to real content scenarios. This approach enables repeatable PR validation and robust contracts between authors and developers.