Gatsby's roadmap and its future
summary
Gatsby claims that large sites no longer need O(n) full rebuilds: incremental builds on Gatsby Cloud rebuild only changed pages (demo shows ~10s full build vs ~1–6s incremental), and a forthcoming streaming builds pipeline aims for sub‑1s updates even with per‑second mutations. It already paralyzes image work, adds native TypeScript, supports many CMS source plugins, and keeps streaming/incremental features tied to Gatsby Cloud today while upstreaming plugins and APIs for broader speed gains.
AI-written summary · about
chapters (5)
related talks
42mGatsby is Evolving
34mWhat is new with Gatsby.js
28mGatsby High Level
19mWhat’s New and What’s Coming?
25mGatsbyJS — How to Create The Fastest Sites In The World
01mWhere We've Been and Where We're Going
27mBeyond Static: Dynamic Web Applications with Gatsby
50mUsing GatsbyJS to build a decoupled (Drupal) website (Live demo)