preview-import

Validate imported AEM Edge Delivery Services content against the original page rendering.

1|6|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/aemsites/summit-portal --skill preview-import-aemsites
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preview-import
Source: https://github.com/aemsites/summit-portal/tree/main/skills/aem/edge-delivery-services/preview-import
Command: npx skills add https://github.com/aemsites/summit-portal --skill preview-import-aemsites

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preview-import enables local validation of imported AEM Edge Delivery Services content by verifying rendering against the original page.

Core Features & Use Cases

  • Start the local development server with the correct HTML folder and verify the preview against the source.
  • Navigate to the provided preview URL and confirm rendering, metadata, and layout parity.
  • Troubleshoot rendering discrepancies by comparing structure, assets, and styles to the original page.

Quick Start

Start the local AEM dev server with the correct html-folder derived from metadata.json, then open the preview URL to verify rendering.

Frequently Asked Questions about preview-import

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

FAQPage Schema
How do I verify imported AEM Edge Delivery Services content locally?

To verify imported AEM Edge Delivery Services content locally, start the local development server with the correct html-folder derived from metadata.json, then navigate to the provided preview URL to compare rendering against the original page.

What is the best way to preview imported AEM pages in a local dev server?

The best way to preview imported AEM pages is to start the local dev server pointing to the html-folder specified in metadata.json, then navigate to the document path to confirm metadata, images, and layout are consistent.

Why does my imported AEM content render differently than the original page?

Imported AEM content renders differently due to discrepancies in structure, assets, or styles. Troubleshoot by comparing the local preview rendering against the original page to identify missing metadata or layout inconsistencies.

Do I need a specific html-folder to start the local AEM preview?

Yes, you need to specify the correct html-folder to start the local AEM preview. This folder is derived from metadata.json and is required to serve the generated HTML for local validation.