preview-import

Preview imported HTML in a local AEM Edge Delivery Services server.

162|67|Updated Feb 5, 2026

Search Tags:#validation #rendering #preview #AEM #screenshot #import #dev-server

Ready to run

npx skills add https://github.com/adobe/skills --skill preview-import-adobe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: preview-import
Source: https://github.com/adobe/skills/tree/main/skills/aem/edge-delivery-services/skills/preview-import
Command: npx skills add https://github.com/adobe/skills --skill preview-import-adobe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a streamlined way to preview and verify content that has been imported into the AEM Edge Delivery Services environment, ensuring visual parity and catching issues early.

Core Features & Use Cases

Preview locally via aem up with the correct html-folder and documentPath
Compare rendered output against the original page using screenshot.png for verification
Troubleshoot rendering discrepancies and verify metadata presence in the page source

Quick Start

Start the local preview by running the workflow after generate-import-html completes. Use the HTML folder path from metadata.json with the aem up command, for example aem up --html-folder us and then open the preview URL to compare rendering with the original page.

Frequently Asked Questions about preview-import

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

FAQPage Schema

How do I preview imported content in the local AEM dev server?▼

To preview imported content in the local AEM dev server, run the `aem up` command with the HTML folder path from metadata.json, such as `aem up --html-folder us`, and open the resulting preview URL to verify rendering.

Why does my imported AEM HTML not match the original page rendering?▼

Imported AEM HTML may not match the original page due to rendering discrepancies during import. You can troubleshoot this by comparing the local preview output against the original page using a screenshot.png file for visual verification.

How do I verify rendering parity for imported AEM Edge Delivery Services pages?▼

You verify rendering parity for imported AEM Edge Delivery Services pages by starting the local preview using the `aem up` command, then comparing the rendered output directly against the original page using the screenshot.png reference image.

Do I need a local AEM dev environment to check imported HTML rendering?▼

Yes, you need a local AEM dev environment to preview and verify imported content. The workflow requires running the local AEM Edge Delivery Services development server to check rendering parity and inspect metadata presence in the page source.

What is the best way to troubleshoot rendering discrepancies in AEM imported content?▼

The best way to troubleshoot rendering discrepancies in AEM imported content is to run the local preview using `aem up` with the correct HTML folder path, compare the output against the original screenshot.png, and verify metadata presence in the page source.

Can I use screenshot.png to verify AEM imported HTML locally?▼

Yes, you can use a screenshot.png file to verify AEM imported HTML locally. The preview workflow compares the rendered output from the local AEM dev server against this screenshot to catch visual parity issues early.