preview-import

Verify local HTML previews against original pages using AEM CLI.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/thojava/baco --skill preview-import-thojava
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preview-import
Source: https://github.com/thojava/baco/tree/main/.skills/preview-import
Command: npx skills add https://github.com/thojava/baco --skill preview-import-thojava

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preview and verify imported HTML content in a local AEM Edge Delivery dev server, ensuring rendering matches the original page and enabling quick troubleshooting of issues.

Core Features & Use Cases

  • Start a local development server for the imported HTML bundle using the HTML-folder flag
  • Navigate to preview URLs and compare rendering against the source page (including images and layout)
  • Troubleshoot common issues by verifying blocks, metadata, and assets

Quick Start

Start the development server for the imported HTML folder using aem up --html-folder {dirPath} and then open the preview URL to 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 imported HTML content locally using the AEM CLI?

To preview imported HTML content locally, start the AEM Edge Delivery dev server using the command aem up --html-folder {dirPath} and then open the generated preview URL to verify rendering and images against the original page.

Why does my imported content not render correctly in the local AEM dev server?

Rendering issues in the local AEM dev server often stem from incorrect document paths, missing images, or incomplete metadata.json files required for URL construction during the HTML import workflow.

What do I need to set up before verifying local previews of imported HTML?

You need an installed AEM CLI, a local dev server running, and an imported HTML folder containing an images directory and metadata.json for URL construction to verify local previews.

Can I troubleshoot AEM Edge Delivery block rendering against the original page locally?

Yes, you can troubleshoot AEM Edge Delivery block rendering locally by navigating to the preview URL generated by the dev server and comparing the layout and assets against the original source page.

What is the best way to verify images and metadata during an AEM HTML import?

The best way to verify images and metadata during an AEM HTML import is to start the local development server with the specified html folder and visually compare the output against the source page.