page-decomposition

Page decomposition analyzes a section's content sequences and breaking points to produce neutral descriptions for AEM Edge Delivery Services. It processes section visuals, descriptions, and cleaned HTML to locate boundaries between default content and blocks for informed authoring decisions.

Decomposing a page section requires section visuals as a screenshot, a section description, and cleaned HTML as inputs. Processing these inputs locates sequence boundaries and outputs a structured sequences report suitable for subsequent content-modeling steps.

Finding breaking points between default content and blocks involves analyzing each individual section during the identify-page-structure workflow. Evaluating content sequences determines exact boundaries and outputs a structured sequences report to guide authoring decisions.

Page decomposition applies to each individual section rather than processing multiple sections in a single pass. Invoking it per section during the identify-page-structure workflow ensures accurate sequence boundaries and localized neutral descriptions for content imports.

Cleaned HTML is required for page section analysis to accurately identify content sequences and breaking points. Raw HTML contains structural noise that interferes with locating sequence boundaries, which are essential for generating a reliable structured sequences report.

The best way to prepare content for subsequent modeling steps is to run a section-by-section decomposition that outputs a structured sequences report. This report maps exact breaking points and neutral descriptions needed to transition smoothly into the content-modeling phase.