page-import

Orchestrate web page scraping, structure analysis, and HTML generation for AEM Edge Delivery Services.

Updated Mar 27, 2025
One-click install
npx skills add https://github.com/jfoxx/residentportal --skill page-import-jfoxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: page-import
Source: https://github.com/jfoxx/residentportal/tree/main/.skills/page-import
Command: npx skills add https://github.com/jfoxx/residentportal --skill page-import-jfoxx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of migrating existing web pages into a structured format suitable for AEM Edge Delivery Services, saving significant manual effort.

Core Features & Use Cases

  • Web Page Scraping: Extracts content, metadata, and images from a given URL.
  • Structure Analysis: Identifies page sections and content sequences.
  • Authoring Decision Support: Helps decide between default content and existing blocks.
  • HTML Generation: Creates structured HTML files for AEM EDS.
  • Preview & Verification: Allows for local preview and comparison with the original page.
  • Use Case: Migrate a competitor's landing page to your AEM EDS site by scraping it, analyzing its structure, mapping content to your existing blocks, and generating the final HTML.

Quick Start

Use the page-import skill to migrate the webpage located at https://www.example.com/landing-page.

Frequently Asked Questions about page-import

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

FAQPage Schema
How do I import an existing web page into AEM Edge Delivery Services?

To import a web page into AEM Edge Delivery Services, the page-import skill orchestrates scraping, structural analysis, and HTML generation to migrate content sequentially. It extracts main content sections while skipping headers and footers. You provide a target URL, and the skill coordinates sub-skills to scrape the webpage, identify page structure, and generate the final HTML files for AEM EDS.

What is the process for website migration to AEM EDS using page scraping?

Website migration via page scraping involves extracting content, metadata, and images from a given URL, then analyzing page sections and content sequences. The process identifies whether to use default content or existing blocks, generates structured HTML files, and allows local preview to compare the imported result with the original page before finalizing.

Can I migrate a competitor's landing page to my AEM EDS site by scraping it?

Yes, you can migrate a competitor's landing page to AEM EDS. The skill scrapes the target URL, analyzes its structure, maps the extracted content to your existing blocks, and generates structured HTML. This automates the migration of main content sections while adhering to David's Model for the authoring experience.

Does the page migration process support mapping scraped content to existing blocks?

Yes, the page migration process includes authoring decision support to help map scraped content to existing blocks or default content. During structural analysis, the skill identifies page sections and content sequences, guiding authoring decisions to ensure the generated HTML aligns with available blocks in your AEM EDS environment.

What are the limitations of web page import for AEM EDS regarding page sections?

The web page import for AEM EDS focuses on migrating main content sections while explicitly skipping headers and footers. It requires sequential invocation of sub-skills like scrape-webpage, identify-page-structure, authoring-analysis, generate-import-html, and preview-import to complete the process, meaning it handles single web pages rather than full site migrations.

How do I preview and verify imported HTML against the original web page?

To preview and verify imported HTML, the skill includes a preview-import sub-step that allows for local preview and comparison with the original page. This verification step occurs after HTML generation, ensuring the structured output matches the source content before the migration to AEM Edge Delivery Services is finalized.