generate-migration-html

Generate Edge Delivery Services-compliant HTML from authoring analysis.

Updated Sep 12, 2025
One-click install
npx skills add https://github.com/ComwrapUkReply/ue-multitenant-root --skill generate-migration-html
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-migration-html
Source: https://github.com/ComwrapUkReply/ue-multitenant-root/tree/main/.claude/skills/generate-migration-html
Command: npx skills add https://github.com/ComwrapUkReply/ue-multitenant-root --skill generate-migration-html

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates Edge Delivery Services-compliant HTML from authoring analysis, creating section structure, applying block tables, and managing images folders to preserve content fidelity.

Core Features & Use Cases

  • Creates section-level markup with div-based blocks and metadata blocks aligned to authoring-analysis decisions
  • Enforces the HTML generation workflow: section content, blocks, and section metadata while respecting image and asset placement
  • Supports image-folder management and path conventions per migration rules for per-page HTML output

Quick Start

Provide the complete authoring analysis and cleaned HTML together with metadata to generate the full HTML migration output.

Frequently Asked Questions about generate-migration-html

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

FAQPage Schema
How do I generate Edge Delivery Services-compliant HTML for page migration?

To generate Edge Delivery Services-compliant HTML for page migration, provide complete authoring analysis, section styling validation, and cleaned HTML to enforce required structure, section blocks, and metadata placement.

What is the correct way to structure section-metadata blocks in Edge Delivery HTML?

Section-metadata blocks in Edge Delivery HTML must be placed accurately within section markup to align with authoring-analysis decisions, ensuring proper div-based block structure and metadata compliance for successful page migration.

How do I manage image folder paths and placement during content migration to Edge Delivery?

Managing image folder paths during content migration requires enforcing specific path conventions and per-page HTML output rules to ensure correct image and asset placement within the Edge Delivery Services structure.

What prerequisites are needed to create section-level markup for Edge Delivery pages?

Creating section-level markup for Edge Delivery pages requires complete authoring analysis, section styling validation, and cleaned HTML as inputs to accurately apply div-based blocks and section-metadata placement.

Why does my migrated HTML fail Edge Delivery Services structural validation?

Migrated HTML fails Edge Delivery Services structural validation when section content, blocks, and section-metadata are not properly structured according to the required HTML generation workflow and authoring-analysis decisions.

Can I use cleaned HTML directly for Edge Delivery page migration without authoring analysis?

No, Edge Delivery page migration requires both cleaned HTML and complete authoring analysis together with metadata to generate the full HTML migration output and enforce the required section structure.