Automate AEM demo documentation generation with dialog captures and previews.
npx skills add https://github.com/easingthemes/dx-aem-flow --skill aem-doc-gen
Please help me install this Agent Skill. Skill: aem-doc-gen Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-aem/skills/aem-doc-gen Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill aem-doc-gen
Manually creating AEM demo documentation and authoring guides is time-consuming and error-prone. This Skill automates end-to-end generation, ensuring consistent structure across components.
Create a demo by running the aem-doc-gen skill against the target work item to generate the docs page and authoring guide.
High-intent search queries and answers about installing and using this skill.
Automating AEM documentation requires configuration-driven URLs to generate authoring guides, capture dialog screenshots, and attach rendered previews. This pipeline executes end-to-end across local and QA environments using aem-inspector and editorial-capture agents.
Capturing dialog screenshots for AEM components is automated by applying configuration-driven URLs and the editorial-capture agent. The process extracts spec data, generates an authoring guide, and attaches rendered previews for target demo pages.
Generating AEM demo docs requires configuration-driven URLs and the aem-inspector or editorial-capture agents to execute tasks. It supports local and QA environments, applying graceful degradation when AEM is unavailable.
Generating authoring guides for AEM components in a local environment is fully supported alongside QA environments. The automation discovers spec data and configuration, creating consistent documentation pipelines with graceful degradation if AEM is unavailable.
AEM documentation automation handles unavailable environments through graceful degradation, allowing partial spec data discovery and configuration processing. Manual creation is error-prone, making this automated fallback necessary to maintain documentation consistency.
An AEM documentation pipeline for component page creation includes spec data discovery, authoring guide generation, dialog screenshot capture, and rendered preview attachment. It relies on configuration-driven URLs and specialized agents to execute the end-to-end workflow.
easingthemesVerify deployed AEM components by walking dialog fields and saving verification docs.
easingthemesGenerate editor-friendly authoring guides from AEM component dialogs.
thktAutomate browser interactions for E2E testing, screenshots, and data extraction.
Orpheus-KGenerate VitePress documentation, API tables, and usage examples for Lucky UI components.
