AEM Edge Delivery Services (EDS) Technology Stack
CMS:
AEM EDS
Overview
Section titled “Overview”Adobe’s Edge Delivery Services (formerly Franklin/Helix) — document- authored, build-step-free sites optimized for top-tier performance, chosen when speed-to-market and Core Web Vitals are the priority over deep custom authoring workflows.
Stack by layer
Section titled “Stack by layer”| Layer | Technology / Tool | Notes |
|---|---|---|
| Backend/Platform | Adobe App Builder (Adobe I/O Runtime) | Serverless functions for backend logic & integrations |
| Frontend | Vanilla JS (ES Modules) | No build step; core EDS block architecture |
| Frontend | Preact | More complex interactive components |
| Frontend | Dropin development (e.g. Adobe Commerce Dropins) | Reusable, framework-agnostic prebuilt component pattern |
| Frontend | Universal Editor | Blocks instrumented for in-context editing |
| Testing & QA | Lighthouse CI | Core to EDS’s performance value proposition |
| Testing & QA | Playwright | E2E testing |
| CI/CD & tooling | GitHub Actions | Native pairing; source repo is GitHub |
| CI/CD & tooling | @adobe/aem-cli | Local dev server & tooling |
| CI/CD & tooling | helix-importer | Content migration tooling |
| Infrastructure & hosting | Adobe Edge Delivery (Fastly-based) | Adobe-managed CDN/edge; no separate hosting to provision |
Content authoring/modeling tooling is intentionally excluded —
authoring workflows and content modeling are the content team’s remit,
not development’s. Content may originate in Word/Google Docs or
directly in AEM, depending on the project. See also
shared-stack.md for cross-cutting tools (version
control, testing, design handoff) that apply here too — note EDS’s
CI/CD and version control already default to GitHub, matching the
shared stack.