Building next gen composable services with Experience Manager
summary
Adobe claims a performance target of 95% of visitors get LCP <2.5s by combining client-side optimization with a new Edge publishing delivery service that runs code natively on the edge (reducing origin lookups). Content becomes “bottomless”: Google Drive, SharePoint and GitHub can serve as sources while AEM provides CMS services. A Universal Editor instruments any front end (even React) to edit live pages, includes generative text editing, and supports rapid VIP projects that ship prototypes in as little as two weeks.
AI-written summary · about
chapters (8)
- 0:00Welcome and introductions
- 3:40Exceptional web experiences
- 11:23Web platform modernization
- 22:53Edge publishing and delivery
- 28:55VIP productization process
- 36:12The bottomless CMS concept
- 41:09Universal editor demonstrations
- 58:50Closing and session previews
related talks
46mThe Past, Present, and Future of Adobe Experience Manager
52mKeynote: Headless Today & Tomorrow with Adobe Experience Manager
54mAdobe Experience Manager Rock Star: The Headless Challenge
32mHeadless Adobe Experience Manager Sites
39mAdobe Experience Manager as a Headless CMS - Where/When/Why?
44mTop 10 Tips to Speed Up Your Adobe Experience Manager Site
02mAEM Shorts: Modernizing Your AEM Implementation with Cloud Service
02mAEM Shorts: Driving Headless Experiences with AEM