'I need it yesterday!' - The secret story of MDS
summary
A design system of 50 reusable components anchors a migration from PHP to Nuxt/Next server‑side rendering and a monorepo, powering portals with over 1 million URLs and 26M total views. Practical fixes include linters, SSR layering, partial hydration, build‑time JSON caching and a dynamic‑render hack for web vitals. Debugging uncovers surprising failures — an Algolia plugin plus Apollo vue‑meta and Google Tag Manager bugs cause a memory leak after ~100 page views — and the rebuilt portal now runs and inherits updates.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:19MDS case study
- 4:52Agency to tech stack
- 9:31Design system & linters
- 13:03Portal redesign & Next.js
- 14:49Memory leak discovery
- 17:46Debugging memory leak
- 20:16New portal launch
- 23:22Performance plugins
- 24:46Results & outcomes
- 25:58Q&A
related talks
36mNuxt as the backbone of a scalable e-commerce platform
21mHow to enable large scale collaboration between disciplines using Nuxt
27mDX is the new black. Learnings from using Nuxt and Storybook at scale
44mNuxt.js - Why? How? Oh yeah!
08mManaging a Large in Place Migration to Nuxt js
44mServer Side Rendering from the trenches
22mDeep dive into Nuxt.js
32mUnderstand the hard parts of Nuxt