Migrating Notion’s marketing site to Next.js
summary
Notion migrates its marketing site from client‑rendered app code to a fully static Next.js build, reusing React but changing routing with a reverse proxy and deploying a Docker container on AWS ECS. Migration moves 200,000 lines of code, 109 components, 23 static and 129 dynamic pages over two months with two engineers. Results: homepage JS drops 9.1 MB → 847 KB (93%), Lighthouse rises ~50 to 97, no loading spinners, Cloudflare caching and incremental static regeneration in place.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:05Pain points
- 5:20Migration scope
- 6:58Reverse proxy
- 11:31User experience
- 12:20Developer experience
related talks
10mHow to migrate 50,000 lines of code to React Server Components
31m'I need it yesterday!' - The secret story of MDS
27mAn introduction to Next.js and what's to come in 2021
10mGradual Migration Strategies for Next.js
22mHow micro-frontends and NextJS can 4x site performance
30mWhen NOT to Use Next.js
13mSpeed at Scale: Optimizing The Largest CX Platform Out There
19mMoving from a React SPA to Next