skills.rest
ak8458
ak8458COMMUNITY
Explore all skills by this author →
GitHub

preview-import

Preview and validate imported HTML rendering in a local AEM Edge Delivery Services dev server.

Updated Jan 13, 2026
Search Tags:#troubleshooting#rendering#verification#preview#aem#import#edge-delivery
One-click install
npx skills add https://github.com/ak8458/abc-boilerplate --skill preview-import-ak8458
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: preview-import
Source: https://github.com/ak8458/abc-boilerplate/tree/main/.skills/preview-import
Command: npx skills add https://github.com/ak8458/abc-boilerplate --skill preview-import-ak8458

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preview and validate imported content in a local AEM Edge Delivery Services dev server. It ensures rendering aligns with the original page and helps identify and troubleshoot discrepancies.

Core Features & Use Cases

  • Validate rendering fidelity by comparing the preview against the source page.
  • Step through a local dev workflow: start the AEM proxy, load the preview URL, and check structure, assets, and metadata.
  • Troubleshoot common issues such as missing assets, styling drift, or mismatched DOM structure.

Quick Start

Start the local AEM proxy with aem up, then open the preview URL for your document path and verify rendering against 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 and verify imported content in AEM Edge Delivery Services?▼

You can preview imported content by running `aem up` to start the local AEM proxy, then opening the preview URL for your document path. This allows you to validate rendering fidelity and check structure, assets, and metadata against the original page.

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

Rendering discrepancies usually arise from missing assets, styling drift, or mismatched DOM structure. Load the preview URL in your local AEM dev server and compare the output against the source page to troubleshoot these issues.

What do I need to verify rendering fidelity locally in AEM Edge Delivery Services?▼

To verify rendering fidelity locally, you need the AEM dev server running via `aem up`, access to the generated HTML and assets, and a valid `documentPath` configured in `metadata.json`.

How do I troubleshoot missing assets or styling drift in an AEM imported page?▼

Start the AEM proxy with `aem up` and inspect the local preview URL to troubleshoot missing assets or styling drift. Compare the rendered output and DOM structure directly against the original page to pinpoint mismatches.

Can I validate imported HTML structure without a valid documentPath in metadata.json?▼

No, you need a valid `documentPath` in `metadata.json` to validate imported HTML structure. Running `aem up` and accessing the generated HTML are also required to load the preview URL successfully.

Related Skills

Explore More Software Engineering Skills→
initialyzeinitialyze

preview-import

Preview imported HTML on the local AEM dev server and compare rendering.

Official
Basic
treevestreeves

preview-import

Preview and validate imported HTML content in a local AEM Edge Delivery Services environment.

Community
Advanced
aemysitesaemysites

preview-import

Verifies imported HTML in a local DEV environment via automated checks and guided troubleshooting steps.

Official
Intermediate
salvamolasosalvamolaso

preview-import

Preview imported HTML content in a local AEM Edge Delivery dev server.

Community
Basic