Using Content Driven Development

Use a content-first workflow to align AEM Edge Delivery development with real author content. This approach solves code-to-content mismatch by guiding teams to design, implement, and validate blocks against real content models.

Content driven development is a phase-based orchestration workflow for AEM Edge Delivery that ensures development is guided by author needs. It coordinates content modeling, block implementation, and validation to maintain end-to-end alignment.

Validate AEM blocks by creating test content that doubles as author documentation and PR validation references. This test content drives development and ensures blocks are tested against real content models.

Yes, jsdom is a required dependency for executing this content-first AEM workflow. It provides the environment needed to run the scripts that orchestrate content modeling, block implementation, and validation phases.

Start content modeling for AEM blocks by describing the target block and its content model, then create test content to drive development. This quick start approach ensures implementation follows real author requirements.