Why does this skill use neutral descriptions instead of block names?

Neutral descriptions prevent premature implementation decisions. By describing 'what' is seen rather than naming a 'block', it allows the content-modeling process to choose the most appropriate component based on the full inventory later.

What qualifies as a 'breaking point' in a section?

A breaking point is a visual or semantic shift, such as moving from standard prose text to a structured grid, or changing from one repeating pattern (like cards) to a different layout.

Does this skill analyze the entire page at once?

No, it is designed to be invoked per section. It focuses on the internal structure of a single section at a time to ensure high accuracy and manageable complexity during the decomposition process.

How does this skill integrate with Adobe Edge Delivery Services?

It acts as a middle-ware step in a page-import workflow, identifying the sequences that will eventually become either 'Default Content' or specific 'Blocks' in the EDS authoring environment.

AEM EDS Page Decomposition

Name: AEM EDS Page Decomposition
Author: ddttom

byddttom

•

Content Management

Analyzes content sequences within sections to provide neutral structural descriptions for AEM Edge Delivery Services page imports.

About

This skill is a specialized component of the AEM Edge Delivery Services (EDS) migration workflow, designed to analyze individual page sections and identify internal content patterns. By breaking down sections into neutral content sequences and identifying visual shift points, it creates a structured foundation for future block mapping and content modeling. It allows developers and content architects to describe exactly what is seen on a page—such as grids, stacked buttons, or prose—without prematurely assigning specific component names, ensuring a more accurate and flexible migration process.

Key Features

Generates neutral, description-based content sequences for objective analysis
Analyzes layout hierarchies and quantities without implementation bias
Identifies visual and semantic breaking points within page sections
Differentiates between default content flows and structured patterns
5 GitHub stars
Provides structured JSON output to support downstream authoring decisions

Use Cases

Automating the content migration process from legacy websites to AEM EDS
Generating structured section metadata for content-driven development workflows
Auditing existing web page structures for componentization and block mapping

About

Key Features

Generates neutral, description-based content sequences for objective analysis
Analyzes layout hierarchies and quantities without implementation bias
Identifies visual and semantic breaking points within page sections
Differentiates between default content flows and structured patterns
5 GitHub stars
Provides structured JSON output to support downstream authoring decisions

Use Cases

Automating the content migration process from legacy websites to AEM EDS
Generating structured section metadata for content-driven development workflows
Auditing existing web page structures for componentization and block mapping