find-test-content

To find pages containing a specific AEM block, query the /query-index.json endpoint and inspect each page for block-related CSS classes to surface matching URLs and variant counts. This enables efficient test-driven content validation by locating diverse test contexts.

The best way to locate test content blocks across local dev environments is to run a script that queries the site index and performs headless HTML parsing. It identifies block-related classes and reports variant counts to support testing workflows.

Yes, you can use query-index to extract block variant data from live preview hosts. The skill operates on both local development servers and live previews by fetching and parsing HTML to identify block-related classes and variant information.

Yes, jsdom is required to inspect pages for block-related CSS classes. The skill relies on jsdom as a dependency for headless fetch and parsing of HTML to extract variant data and report matching page URLs.

Querying test content across pages requires a resilient concurrency model to handle headless fetch operations efficiently when inspecting numerous pages for block-related classes. This ensures reliable extraction of variant data without failing during bulk page processing.