block-inventory

To discover available blocks in an AEM Edge Delivery Services project, run a directory listing to survey local blocks and use parallel Node.js scripts to search the Block Collection, returning a structured block inventory with purposes and example URLs.

A block inventory is a consolidated list of local and discoverable blocks with descriptions and example URLs. You need it for content modeling when planning a new website project to identify pre-built components and inform content structure decisions.

Yes, you can search the Block Collection for common block types using parallel Node.js scripts. The process queries the central repository for reusable blocks and consolidates the findings into a structured output detailing discoverable blocks with descriptions.

Yes, the block discovery process works with local AEM Edge Delivery Services projects by identifying local blocks via directory listing. It surveys the current project to understand the available block palette for authoring.

The best way to find pre-built components like hero or cards is to survey local project blocks and search the Block Collection. This identifies available blocks and their purposes, allowing for faster content planning and development.

The limitation of identifying block purposes is that the process derives or infers descriptions from available local blocks and the Block Collection, meaning the accuracy depends on the existing metadata and structure of the discovered blocks.