Changing The Game with Developer Experience
summary
Documentation site is statically generated with Next.js and served from Vercel’s Edge CDN, achieving 100/100 Lighthouse and instant page loads; API reference is auto‑generated from a single open API 3,500‑line spec fetched from GitHub so docs update when code merges; pages come from markdown via getStaticPaths; selected text creates a GitHub issue and a feedback modal captures screenshots which the site uploads and posts as issues, closing the feedback loop.
AI-written summary · about
chapters (16)
- 0:00Developer experience and docs
- 1:03Documentation critical for DX
- 2:24Problems with traditional docs
- 3:49World-class documentation
- 5:37Static site generation for docs
- 6:41Automating docs updates
- 7:25Impactful docs with instant feedback
- 8:08Live docs demo
- 9:13Performance with Lighthouse
- 9:56API docs from OpenAPI
- 13:34Next.js docs code walkthrough
- 16:31OpenAPI specs for API docs
- 19:46Advanced docs feedback
- 22:34Key DX takeaways
- 24:21Reducing human error
- 25:02Closing remarks
related talks
42mEngineering Documentation
21mWriting documentations that don't suck!
39mDevelopers Documentation: your hidden strength
35mDev Experience in Technical Writing: 15 Tips to Boost Developer Satisfaction
44mUseful and Beautiful Developer Docs and How to Create Them
47mEngineering Documentation
43mUseful and Beautiful Developer Docs and How to Create Them
40mFrom resistance to adoption: navigating the challenges of docs-like-code