Experience Manager Extension for PWA Studio
summary
Extension adds AEM as a second GraphQL endpoint to PWA Studio, exposing Content Fragments and GraphQL API so a blog page and product-detail overlays pull wholly managed AEM content. Implementation uses the Apollo client target routing to send queries to either Adobe Commerce or AEM, and ties product fragments to catalog items via Commerce Integration Framework (CIF). Demo shows a working blog and PDP enrichment; expect cache/service-worker nuances and increased client complexity with more endpoints.
AI-written summary · about
chapters (12)
- 0:00Introduction to session
- 1:24Headless options in AEM
- 7:43AEM extension overview
- 10:13Demo of content page
- 14:30Demo of enriched commerce page
- 16:44Technical deep dive
- 21:38PWA Studio extension details
- 23:05GraphQL endpoint integration
- 24:29Extension mechanisms
- 27:21When to use this approach
- 28:45Alternative architectures
- 29:10Q&A and conclusion
related talks
39mAdobe Experience Manager as a Headless CMS - Where/When/Why?
54mAdobe Experience Manager Rock Star: The Headless Challenge
27mBuild Your First React App with Experience Manager Headless CMS
02mAEM Shorts: Driving Headless Experiences with AEM
38mSeamless Integration of Experience Manager Assets with Applications
52mKeynote: Headless Today & Tomorrow with Adobe Experience Manager
01h 00mBuilding next gen composable services with Experience Manager
36mHow to Build Content and Commerce Experiences Using App Builder and API Mesh