What problem does it solve?
Determine whether each content sequence on a page should be authored as simple default content or implemented as a structured block to ensure correct import, consistent authoring, and reliable HTML generation for AEM Edge Delivery Services. This prevents mismatches between author intent and block structure that cause layout errors, incorrect decoration, or unnecessary section metadata.
Core Features & Use Cases
- Per-sequence authoring decisions: Implements a mandatory default-content-first check, then a block-selection decision tree to classify sequences.
- Validation and discovery: Triggers content-modeling for ambiguous cases and invokes block-collection checks when blocks are missing from the inventory.
- Section styling validation: Executes a focused step for single-block sections to decide whether to keep or skip section-level metadata based on screenshot analysis.
- Use Case: During a page-import workflow, analyze identified sections, sequences, and a block inventory to produce a deterministic mapping of default content vs blocks and a validated section-styling plan for downstream HTML generation.
Quick Start
Run authoring analysis on the identified page structure, content sequences, block inventory, and screenshot to produce sequence decisions and validated section-styling.
