"Lessons Learned Migrating from Jekyll to Next.js with Help from Playwright"
summary
Migration moves a Jekyll site into Next.js, preserves existing markdown collections and nearly about 1,000 blog posts, and validates fidelity with Playwright screenshot comparisons. Tests hit critical pages across 20 viewport sizes, generate lots of images (about 650 MB of golden masters), and run in CI: a 2‑core worker takes ~1 hour while a 32‑core runner finishes in ~3 minutes. Static builds serve snapshots for comparison, RSS and metadata are verified, and some performance and build-time tradeoffs remain.
AI-written summary · about
chapters (7)
- 0:00Platform migration journey
- 3:56Migration philosophy
- 13:08Validating with Playwright
- 21:58Incremental process
- 27:19Migration pros and cons
- 29:45Future plans
- 31:09Q&A
related talks
14mRewriting eaze.com with Next.js
01h 31mAdvanced Playwright with AI
18mAt the top of the pyramid: Playwright testing at scale
12mPlay It Right With Playwright
25mPlaywright Test Runner
48mHow We Tried to Introduce E2E Tests and Why It Failed
31mStop Guessing A11y: Auto-Generate Playwright Tests from Your GraphQL Schema
11mHow to make cheap e2e tests