Adobe Experience Manager as a Headless CMS - Where/When/Why?
summary
Shows concrete AEM headless patterns: using content fragments (master + variations) for personalization (gold/platinum) and multi-screen reuse, serializing to JSON via Sling exporter/servlets or HTTP API, and querying with GraphQL for SPAs and mobile. Demoed asset API and GraphQL flows, an Angular SPA wired to the AEM JSON model, and SPA Editor integration; notes SPA Editor requires frontend stack knowledge and has a learning curve. Reports real usage (including a cited ~50 million content fragments) and that exporters work in production while SPA Editor is experimental.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 1:30Headless vs traditional CMS
- 4:34When to use multi-page vs SPA
- 7:57Headless options in AEM
- 14:10Content fragments use cases
- 23:18SPA Editor overview
- 25:18Angular SPA implementation demo
- 32:20Q&A and closing remarks
related talks
32mHeadless Adobe Experience Manager Sites
46mThe Past, Present, and Future of Adobe Experience Manager
30mExperience Manager Extension for PWA Studio
25mAdobe Experience Manager Forms as a Cloud Service
01h 00mBuilding next gen composable services with Experience Manager
38mSeamless Integration of Experience Manager Assets with Applications
35mApp Builder Architecture and Technical Deep Dive
54mFireside Chat with Experience Manager Product Leaders