eds-cicd-pipeline

Setting up GitHub Actions CI/CD for AEM Edge Delivery Services involves generating EDS-specific workflows that enforce ESLint, CSS validation, HTML validation, and link checking as automated quality gates. This replaces artifact-based builds with continuous code quality checks for your EDS project.

Lighthouse CI prevents performance regressions in AEM Edge Delivery Services by applying EDS-appropriate thresholds and running audits against preview URLs. It generates PR reporting within GitHub Actions to catch SEO and performance issues before changes reach production.

Yes, you can automate preview and publish updates using the AEM Admin API in GitHub Actions. The generated workflows optionally trigger preview and publish updates after merges, complete with documented safety checks and rate-limiting behavior to protect your EDS deployment.

No, you do not need an existing AEM Edge Delivery Services project to use these CI quality gates. The generated workflows and configurations apply to both new and existing EDS projects that need automated linting, link validation, and Lighthouse CI checks.

The ESLint rules enforced for AEM Edge Delivery Services code are based on the Airbnb configuration with specific EDS overrides. This ensures your JavaScript and code structure meet strict quality standards while accommodating the unique requirements of EDS repositories.

Link-check crawlers in EDS GitHub Actions workflows work by automatically validating URLs within your repository to identify broken links. The generated configuration scans your content to ensure all internal and external references remain valid before changes reach production.