skills.rest
juricamigac-from-hr
juricamigac-from-hrOFFICIAL
Explore all skills by this author →
GitHub

preview-import

Preview and validate imported HTML content on a local AEM Edge Delivery Services dev server.

Updated Apr 5, 2026
Search Tags:#rendering#verification#preview#aem#import#edge-delivery#dev-server
One-click install
npx skills add https://github.com/juricamigac-from-hr/svemojestrane --skill preview-import-juricamigac-from-hr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: preview-import
Source: https://github.com/juricamigac-from-hr/svemojestrane/tree/main/.agents/skills/preview-import
Command: npx skills add https://github.com/juricamigac-from-hr/svemojestrane --skill preview-import-juricamigac-from-hr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables QA and development teams to preview and validate content imported into the local AEM Edge Delivery Services dev server, ensuring the rendered output matches the original source and quickly identifying issues.

Core Features & Use Cases

  • Preview imported HTML in a local dev server to confirm rendering and structure.
  • Compare the local preview against the original page and troubleshoot discrepancies.
  • Use with generated HTML/import workflows to validate assets and metadata before deployment.

Quick Start

Open the local development server and verify the imported content renders correctly.

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 on a local AEM Edge Delivery Services dev server?▼

To validate imported HTML locally, open the AEM Edge Delivery Services dev server and load the generated HTML file. You must place an images folder, screenshot.png, and metadata.json in the same directory to verify rendering fidelity and page structure.

What files do I need to validate imported AEM content locally?▼

Validating imported AEM content requires an HTML file at the correct path, an images folder in the same directory, a screenshot.png from the scrape-web-page step, and a documentPath from metadata.json to construct URLs.

How does local dev server rendering verification work for AEM imports?▼

Rendering verification works by comparing the local dev server output against the original page screenshot. This troubleshooting process helps identify discrepancies across import-generated HTML, assets, and metadata before deployment.

Why does my imported AEM Edge Delivery Services content not render correctly locally?▼

Imported AEM content fails to render correctly locally if the HTML file path is incorrect, the images folder is missing from the same directory, or the documentPath from metadata.json cannot construct valid URLs for the dev server.

Can I use the local AEM dev server to troubleshoot import-generated metadata and assets?▼

Yes, you can use the local AEM dev server to troubleshoot import-generated metadata and assets. It allows you to preview and validate content locally to quickly identify rendering discrepancies and structural issues before deployment.

Related Skills

Explore More Software Engineering Skills→
pragyaP17pragyaP17

preview-import

Start the local AEM dev server and preview imported HTML for verification.

Community
Basic
ak8458ak8458

preview-import

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

Community
Intermediate
initialyzeinitialyze

preview-import

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

Official
Basic
adobeadobe
162

preview-import

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

Official
Advanced