How to enable large scale collaboration between disciplines using Nuxt
summary
Shows converting a giant e‑commerce monolith into a Nuxt‑based front‑end platform that runs in production, with teams owning micro apps but sharing a single component library, a headless CMS via an adapter and a central content service that validates and stores page schemas. Uses Vue components, Nuxt renderer and lazy loading via the component module to avoid shipping everything. Claims editorial workflow becomes 10× faster and cross‑team churn and release friction drop dramatically.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:41Jumbo and e-commerce evolution
- 3:08Monolith to component architecture
- 6:57Frontend platform challenges
- 8:21Choosing Nuxt for platform
- 9:46Component library foundation
- 11:31Headless CMS integration
- 12:36Content service role
- 13:59Renderer layer with Nuxt
- 16:30Key challenges and solutions
- 18:38Platform benefits summary
- 20:04Closing and Q&A
related talks
36mNuxt as the backbone of a scalable e-commerce platform
38mLarge Scale Nuxt Architecture
27mDX is the new black. Learnings from using Nuxt and Storybook at scale
08mManaging a Large in Place Migration to Nuxt js
36mThe biggest eCommerce Vue project with Composition API
55mNuxt.js: isomorphic Vue.js Apps made easy, fast and fun
26mBe Lazy, Be Smart, Be Nuxt.
31m'I need it yesterday!' - The secret story of MDS