identify-page-structure

To identify page structure for AEM Edge Delivery Services imports, apply a two-level analysis to scraped webpage content that detects section boundaries and maps per-section content sequences from the provided HTML and metadata inputs.

Mapping content sequences and section boundaries requires three specific inputs: a screenshot.png file for visual reference, a cleaned.html file for structural markup, and a metadata.json file containing the scraped webpage's contextual details.

Section identification works by applying a two-level analysis that first determines section boundaries across the page, then extracts the specific content sequences within each section to produce neutral descriptions for downstream authoring decisions.

Yes, webpage structure mapping for AEM imports includes a block inventory step that surveys available blocks within the identified sections, providing a comprehensive overview to inform downstream authoring decisions.

The best way to extract a two-level page structure from cleaned HTML is to process the markup through a section identification routine that outputs neutral section-level descriptions alongside detailed per-section content sequences for downstream use.

Yes, this page structure mapping approach works without external dependencies, requiring only the standard screenshot.png, cleaned.html, and metadata.json inputs to generate section boundaries and content sequences for AEM Edge Delivery Services.