generate-import-html

Generate structured HTML with block tables and metadata for AEM Edge Delivery Services page imports.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aemgdc/aemdev --skill generate-import-html-aemgdc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generate-import-html
Source: https://github.com/aemgdc/aemdev/tree/main/.agents/skills/generate-import-html
Command: npx skills add https://github.com/aemgdc/aemdev --skill generate-import-html-aemgdc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Migrating a webpage into AEM Edge Delivery Services requires converting scraped content into the platform's specific plain HTML format with section divs, block tables, and metadata blocks, which is tedious and error-prone to do by hand. ## Core Features & Use Cases - Section and Block HTML Generation: Creates one top-level div per section with nested block tables and default content, without html, head, body, header, or footer wrappers. - Metadata Block Mapping: Maps extracted title, description, image, canonical, and tags into a metadata block while omitting properties the platform auto-populates. - Images Folder Management: Copies the scraped images folder next to the generated HTML file and verifies relative image paths resolve correctly. - Use Case: After scraping and analyzing a source page, generate us/en/about.plain.html with all sections, validated section-metadata styling, a metadata block, and a sibling images folder ready for preview. ## Quick Start Generate the import HTML file from the completed authoring analysis and save it with its images folder at the path from metadata.json.

Frequently Asked Questions about generate-import-html

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

FAQPage Schema
How do I generate import HTML for AEM Edge Delivery Services?▼

Generate one top-level div per section containing block tables and default content, with no html, head, body, header, or footer wrappers. Append a metadata block as the last section and save the file at the path from metadata.json.

What metadata should I include in an AEM import metadata block?▼

Include title, description, image, canonical, and tags only when they differ from platform defaults. Skip og:title, og:description, twitter properties, viewport, and charset because the platform auto-populates or handles them in head.html.

Where should the images folder go when importing a page?▼

Place the images folder in the same directory as the generated HTML file. For example, us/en/about.plain.html pairs with us/en/images/, and image references stay as ./images/... so relative paths resolve correctly.

When should I use section-metadata in AEM imports?▼

Apply section-metadata when the section provides container styling such as background or layout, based on validated authoring-analysis decisions. Skip it for single-block sections where the background is block-specific, like a hero with its own dark background.

Why does my AEM page import fail validation?▼

Validation fails when the HTML section count differs from the identified page structure, content is truncated with placeholders, images are missing, or the images folder was not copied next to the HTML file. Fix each failed check before proceeding to preview.