القائمة
Preview and verify imported content in local AEM Edge Delivery Services dev server. Validates rendering, compares with original page, and troubleshoots common issues.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | preview-import |
| description | Preview and verify imported content in local AEM Edge Delivery Services dev server. Validates rendering, compares with original page, and troubleshoots common issues. |
| license | Apache-2.0 |
| metadata | {"version":"2.0.0"} |
Open and verify imported content in local development server.
Use this skill when:
Invoked by: page-import skill (Step 5)
From previous skills, you need:
Determine the folder from metadata.json:
paths.dirPath from metadata.json (e.g., /us)Command:
aem up --html-folder {dirPath}
Examples based on imported content location:
| HTML File Location | Command | Preview URL |
|---|---|---|
us/en.plain.html | aem up --html-folder us | http://localhost:3000/us/en |
products/widget.plain.html | aem up --html-folder products | http://localhost:3000/products/widget |
blog/2024/post.plain.html | aem up --html-folder blog | http://localhost:3000/blog/2024/post |
Why this is required:
--html-folder, AEM CLI proxies requests to the remote serverFor most files, use the document path directly:
http://localhost:3000${documentPath}
Example:
us/en/about.plain.htmlhttp://localhost:3000/us/en/aboutIMPORTANT: For index files, use / instead of /index:
If file is: index.plain.html
Preview at: http://localhost:3000/
NOT: http://localhost:3000/index
Note: If you used --html-folder flag (e.g., aem up --html-folder drafts), prepend that folder to the URL:
File: drafts/test.plain.html
URL: http://localhost:3000/drafts/test
Use paths.documentPath from metadata.json, but for index files ensure the path is / not /index
Check the following:
<meta> tags)Side-by-side comparison:
./import-work/screenshot.png alongside browser previewBlocks don't render correctly:
Images not loading:
./images/... format./import-work/images/Raw HTML visible:
blocks/ directoryMetadata not in page source:
<meta> tags in <head>Dev server not running:
aem upPage not found (404):
--html-folder flag - restart server with aem up --html-folder {dirPath}/index not /This skill provides:
Import complete when all verification points pass.
Analyzes development requirements and generates structured acceptance criteria for AEM Edge Delivery Services (EDS) tasks. Use when the user needs to define acceptance criteria, write requirements, scope work, or create a definition of done for EDS blocks, components, variants, bug fixes, or styling changes. Produces task breakdowns, identifies edge cases, and documents analysis for new blocks, variants, behavior modifications, CSS-only changes, and bug fixes.
Analyze content sequences and determine authoring approach (default content vs blocks). Validates block selection and section styling for import/migration to AEM Edge Delivery Services.
The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration patterns, plugins, and more. Use this skill anytime you are developing something and want to find a reference to use as a starting point.
Survey available blocks from local AEM Edge Delivery Services project and Block Collection to understand the block palette available for authoring. Returns block inventory with purposes to inform content modeling decisions.
Guide for implementing code changes in AEM Edge Delivery Services. Handles block development (new or modified), core functionality changes (scripts.js, styles, delayed.js, etc.), or both. Use this skill for all implementation work guided by the content-driven-development workflow.
Review code for AEM Edge Delivery Services projects. Use at the end of development (before PR) for self-review, or to review pull requests. Validates code quality, performance, accessibility, and adherence to EDS best practices.