The Modern DXP
summary
Claim: every site has a DXP and moving to JAMstack removes the single origin bottleneck. Concrete stack notes: Cloudflare CDN and edge workers, Azure CI, Lambda APIs, Next.js/Nuxt surfacing, Contentful, CommerceTools, Plausible analytics. Built demo shows incremental modernization by “surfacing” legacy pages and injecting modern components so migration avoids full replatforms. Orchestration layer (Uniform) handles personalization at edge or hydration time and delivers personalization without JavaScript, reducing deploy time and vendor lock‑in.
AI-written summary · about
chapters (7)
- 0:00Modern DXP intro
- 3:05Traditional DXP drawbacks
- 10:28Best of breed vs suite
- 16:11Composing DXP with Jamstack
- 18:43Uniform in modern DXPs
- 22:54Legacy to modern DXPs
- 24:18Closing and call to action
related talks
26mInto the Future with Next.js
35mThe Rise of JAMStack
34mHow to JAMstack in a dynamic era
14mThe Movement is Real
40mJAMstack: Silly Name. Serious Stuff
50mDo we really need this JAMstack thing? And what even is it?
11mAddressing deployment speed and developer focus
44mJAMstack: Web Apps at Ludicrous Speed