Headless Adobe Experience Manager Sites
summary
Claims that Adobe Experience Manager can run truly headless using GraphQL for Content Fragments, available for AEM 6.5 and AEM as a Cloud Service, and that teams can build structured, nested content with Content Fragment Models with no Adobe Experience Manager coding. Adobe runs tens of thousands of requests per second through Fastly with a 99.8–99.9% cache hit for Creative Cloud content: about 3–4k original fragments, ~30k total with translations, ~300 models and 100+ authors. Use persistent queries and provided SDKs to keep responses cacheable and low latency.
AI-written summary · about
chapters (8)
- 0:00Introduction to AEM headless
- 3:29Headless implementation case
- 7:41Demo of headless architecture
- 12:06Advanced content modeling
- 17:04Setup and configuration
- 20:56Best practices for development
- 25:12Query optimization and caching
- 29:17Hybrid delivery and conclusion
related talks
52mKeynote: Headless Today & Tomorrow with Adobe Experience Manager
39mAdobe Experience Manager as a Headless CMS - Where/When/Why?
02mAEM Shorts: Driving Headless Experiences with AEM
27mBuild Your First React App with Experience Manager Headless CMS
01h 00mBuilding next gen composable services with Experience Manager
54mAdobe Experience Manager Rock Star: The Headless Challenge
44mTop 10 Tips to Speed Up Your Adobe Experience Manager Site
28mUnderstand GraphQL API performance options and query optimizations