preview-import

Validate imported HTML rendering against original pages in an AEM dev server.

1|Updated Oct 7, 2024
One-click install
npx skills add https://github.com/valithedge/etisalatedge --skill preview-import-valithedge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preview-import
Source: https://github.com/valithedge/etisalatedge/tree/main/.agents/skills/preview-import
Command: npx skills add https://github.com/valithedge/etisalatedge --skill preview-import-valithedge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly validate that imported HTML content renders correctly in a local AEM development server, helping prevent regressions before deployment.

Core Features & Use Cases

  • Quick local preview of imported HTML folders to verify layout, styling, and asset loading.
  • Visual and structural comparison against the original page to catch differences early.
  • Guided troubleshooting steps for common import issues like path resolution and missing assets.

Quick Start

Start the local preview of your imported HTML content using the AEM CLI.

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 in an AEM development server?

To preview imported HTML content in an AEM development server, you can use the AEM CLI to start a local dev server. This allows you to render imported HTML folders and validate layout, styling, and asset loading before deployment.

Why does my AEM imported HTML folder have missing assets and path resolution issues?

Missing assets and path resolution issues during AEM HTML import often stem from incorrect asset references. Guided troubleshooting steps help compare the rendered output against the original page to identify and fix these structural discrepancies.

Can I scope the local preview to a specific imported HTML folder in AEM?

Yes, you can scope the local preview to a specific imported HTML folder in AEM. This optional html-folder scoping ensures the development server only renders and validates the content within your targeted directory.

What is the best way to validate metadata presence and asset references for AEM Edge Delivery content?

The best way to validate metadata presence and asset references for AEM Edge Delivery content is by running a local preview validation. This process checks the imported HTML rendering against the original page to catch differences early.

Do I need the AEM CLI to run a local development server for content validation?

Yes, you need the AEM CLI to ensure the local development server runs properly for content validation. It automates the rendering of imported HTML folders and supports structural comparison against original pages.