Using Content Driven Development

Content-driven development for AEM Edge Delivery ensures code is built against real content and author-friendly models. This approach reduces rework and improves PR validation by enforcing phase-driven processes across discovery, modeling, implementation, and validation.

To create test content for AEM Edge blocks, you can use the CMS or generate local HTML files. Scripts like find-block-content.js support test content creation and automation to enable realistic testing and author documentation before implementation.

Yes, you can validate AEM Edge block changes using local test content or CMS content. The workflow coordinates implementation and validation phases by orchestrating related skills like testing-blocks to ensure code is tested against realistic content models.

The best way to coordinate content-first workflows for block development is to follow a phase-driven process: identify a block, create test content in the CMS or locally, invoke content-modeling and building-blocks workflows, then validate changes using testing-blocks.

Yes, jsdom is a required dependency for the content-driven development workflow. It supports the scripts component used to automate test content creation and validate block decoration functionality during the implementation and validation phases.

You should avoid a content-first approach for AEM Edge projects when real content is unavailable or rapidly changing, as the workflow relies on building code against stable content models to reduce rework and ensure accurate PR validation.