AEM Development Workflow

Enforces a 10-step AEM EDS workflow from content structure to validated PR with demo link.

Updated Nov 5, 2024

Search Tags:#workflow #development #preview #pr #content-first #lint #aem

Ready to run

npx skills add https://github.com/samircaus/elsie --skill aem-development-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: AEM Development Workflow
Source: https://github.com/samircaus/elsie/tree/main/.agents/skills/aem-development-workflow
Command: npx skills add https://github.com/samircaus/elsie --skill aem-development-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AEM EDS has a required development workflow with non-negotiable quality gates. These gates ensure code works in production, not just locally. Skipping gates under pressure leads to broken demos, failed builds, and technical debt.

Core Features & Use Cases

Enforces a content-first, test-first workflow for AEM Edge Delivery Services projects from inception to PR.
Specifies mandatory steps: define content structure, obtain real CMS content, build local HTML scaffolding, implement blocks, lint, test locally, push feature branches, validate in preview with real content, open PR with demo link, and ensure PR checks pass.
Provides guardrails for rapid development while preserving production-quality results, with documented best practices and a strict sequence to avoid technical debt.

Quick Start

Follow the described 10-step workflow to go from idea to validated PR with real CMS content.

Frequently Asked Questions about AEM Development Workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is the required AEM Edge Delivery Services development workflow for new blocks?▼

The AEM EDS development workflow requires a content-first, test-first approach. You must define content structure, obtain real CMS content, build HTML scaffolding, implement blocks, lint, test locally, validate in preview, and open a PR with a demo link.

How do I enforce content-first development for AEM EDS blocks before opening a PR?▼

To enforce content-first AEM EDS development, obtain real CMS content before implementation, build local HTML scaffolding, and validate blocks in the preview environment. This ensures your PR includes a working demo link and passes strict quality gates.

Why does my AEM EDS development workflow require preview validation with real CMS content?▼

Preview validation with real CMS content is required in the AEM EDS workflow to ensure code works in production, not just locally. Skipping this gate leads to broken demos, failed builds, and technical debt under development pressure.

Can I skip linting and testing gates for rapid AEM EDS block development?▼

You cannot skip lint and testing gates during AEM EDS block development. The workflow enforces strict quality gates including lint, content validation, and preview checks to provide guardrails for rapid development while preserving production-quality results.

What are the mandatory steps to go from idea to validated PR in AEM EDS?▼

The mandatory AEM EDS steps to reach a validated PR include defining content structure, getting real CMS content, building scaffolding, implementing blocks, linting, testing locally, pushing feature branches, validating in preview, and ensuring PR checks pass.

Does the AEM Edge Delivery Services workflow support rapid development without technical debt?▼

Yes, the AEM Edge Delivery Services workflow supports rapid development without technical debt by providing documented best practices and a strict 10-step sequence. This enforces mandatory gates like lint and preview validation to preserve production quality.