Verified: 2026-09 against https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/hybrid/spa-editor-deprecation and https://www.aem.live/docs/
This is the single source for "which AEM delivery model should we use". aem-architecture, aem-headless, aem-frontend-development and aem-edge-delivery-services all link here instead of keeping their own copy. Decide per experience, not per company — mixing is normal (an EDS marketing site and a mobile app both reading the same Content Fragments).
The table
| Model | Authoring | Front end | Choose when | Watch out for |
|---|---|---|---|---|
| Traditional Sites — HTL + Core Components | Page editor, in-context | HTL + clientlibs, rendered by publish | Marketing estates with MSM, workflows, CUGs, deep AEM features; large existing component libraries | Front-end work happens inside HTL and clientlibs; page performance depends on dispatcher/CDN tuning |
| Headless — Content Fragments + GraphQL persisted queries | Content Fragment editor (form-based) | Any app you own (Next.js, iOS, kiosk) | One content set feeding several channels; the web front end is not AEM's job | No in-context editing unless you add Universal Editor; persisted queries (GET) are mandatory for CDN caching |
| Hybrid — Universal Editor over your own front end | Universal Editor, in-context | Your React/Next/Astro app, instrumented with data-aue-* |
Authors need visual editing but the front end must live outside AEM | Instrumentation is real work: every editable property needs attributes; preview environment must reach AEM author |
| Edge Delivery Services — document authoring | Google Docs / SharePoint / Document Authoring (da.live) | Blocks in a Git repo, served from the edge | Speed to market, marketing-owned content, a 100 Lighthouse target | No MSM/workflow semantics; auth-gated content and server-side forms need another tier |
| Edge Delivery Services — Universal Editor authoring (xwalk) | Universal Editor against AEM author | Same blocks, content crosswalked from AEM | EDS performance with AEM-managed, structured, translatable content | Block models are declared in JSON (_<block>.json); the project uses the aem-boilerplate-xwalk template |
| SPA Editor (React/Angular in the page editor) | Page editor | SPA in ui.frontend |
Never for new work | Deprecated with AEMaaCS release 2025.01 and 6.5.23; only P1/P2 and security fixes. Existing projects keep running; new builds use Universal Editor |
Deciding questions, in order
- Who authors, and in what tool? Marketing writing in a document → EDS document authoring. Structured records reused across channels → Content Fragments. Page composition with layout control → page editor or Universal Editor.
- Who owns the front end? An existing front-end team with its own stack and release cadence → headless or hybrid. No front-end team → Traditional Sites or EDS.
- Which AEM features are load-bearing? MSM rollouts across many markets, translation projects, workflows, CUGs, Target/Analytics integration via page components — these pull towards Traditional Sites or EDS-with-AEM. A brief that names none of them is a headless candidate.
- What is the performance bar? A contractual Core Web Vitals or Lighthouse target makes EDS the cheapest way to hit it; anything else requires deliberate work on every release.
- Is the content behind a login? Personalised or entitlement-gated content is uncacheable at the edge. Serve the shell from cache and fetch the private part client-side, on any model.
Mixing without regret
- One content model, several deliveries. Content Fragments consumed by GraphQL (app), by HTL components (Sites) and by EDS blocks is a supported and common shape. Model the fragments for the data, not for one channel's layout.
- Experience Fragments are presentational and belong to the page-based models; do not use them as a headless data source.
- Draw the boundary at the URL. Two models on one domain means two origins behind one CDN; decide the path split (
/,/app/*) and the cache rules per path before building. - Record the choice per experience in the ADR with the reason and the date — the platform moves, and "why is the app headless but the site on EDS" is the first question a new team asks.
Dated facts that decide arguments
- SPA Editor is deprecated (AEMaaCS 2025.01, 6.5.23). Universal Editor is the named successor. Do not start new SPA Editor work; migrating an existing SPA Editor project is a Universal Editor instrumentation exercise.
- Universal Editor works with any front end, including plain HTL pages: Core Components emit
data-aue-*instrumentation, so a Sites project needs little or no extra work to open in the Universal Editor. - Content Fragment delivery has two APIs: AEM GraphQL (persisted queries, composed shapes) and the Content Fragment Delivery OpenAPI at
/adobe/contentFragments(REST, single hydrated fragments). See../../headless/aem-headless/SKILL.mdfor the choice.