migrate-header

Migrate website headers into AEM Edge Delivery Services nav.plain.html with scoped CSS.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/aemcoder/skills --skill migrate-header
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-header
Source: https://github.com/aemcoder/skills/tree/main/skills/migration/migrate-header
Command: npx skills add https://github.com/aemcoder/skills --skill migrate-header

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates a source website header/navigation into an AEM Edge Delivery Services (EDS) header block so you can preserve layout and dropdown behavior without manually rebuilding the navigation structure.

Core Features & Use Cases

  • Nav-to-EDS structure generation: Extracts header/nav HTML from a source page and converts it into drafts/nav.plain.html with the correct header block expectations.
  • CSS customization with strict scoping: Produces blocks/header/header.css using .header.block-scoped rules to avoid global overrides and iterates against visual verification.
  • Single-row and multi-section header support: Detects multi-tier headers (brand, top bar, main nav, utility) and transforms dropdowns including mega-menu style content into EDS-compatible structure.
  • Preview-based verification workflow: Uses an EDS project preview page and Playwright checks to ensure hlx/framework loading and the header fragment rendering.

Quick Start

Prompt the system with the source URL and your EDS project path to run the header migration and generate nav.plain.html plus blocks/header/header.css in your target repo.

Frequently Asked Questions about migrate-header

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a website header to an AEM Edge Delivery Services navigation block?

To migrate a website header to AEM Edge Delivery Services, extract the header HTML from a live page and transform it into `nav.plain.html` with scoped `.header.block` CSS. This process preserves dropdowns and mega-menu structures without manual rebuilding.

Can I convert mega-menu and multi-section navigation structures into EDS format?

Yes, you can convert mega-menu and multi-section navigation into EDS format. The migration detects multi-tier headers including brand, top bar, utility links, and main nav, transforming dropdown content into an EDS-compatible structure.

How do I scope CSS for AEM EDS header blocks to avoid global overrides?

To scope CSS for AEM EDS header blocks, generate rules using the `.header.block` selector prefix. This confines styles to the header component, preventing global stylesheet conflicts while matching the existing `blocks/header/header.js` contract.

Do I need Playwright to extract and verify header navigation for EDS?

Yes, Playwright is required to extract and verify header navigation for EDS. It automates live page header extraction and screenshotting, and performs preview-based checks to confirm `hlx` framework loading and header fragment rendering.

What is the best way to verify an AEM EDS header migration is rendering correctly?

The best way to verify an AEM EDS header migration is through a preview-based workflow. This uses an EDS project preview page and Playwright checks to ensure the framework loads properly and the generated header fragment renders correctly.

Does the EDS header migration support single-row headers with utility links?

Yes, EDS header migration supports single-row headers with utility links. It extracts the correct header region from the source page and transforms both simple single-row and complex multi-tier structures into valid EDS markup.