Incremental Static Regeneration (ISR)
Design Processes
Static pages that quietly rebuild themselves in the background when they get stale.
In practice
Incremental static regeneration keeps the speed of a static page while letting content update without a full redeploy: each page carries a revalidation window, and the first visitor after it expires triggers a fresh build behind the scenes while still receiving the cached version. It is how a CMS-driven site can be both static-fast and hours-fresh.
Questions
What is Incremental Static Regeneration (ISR)?
ISR is a rendering strategy where static pages are regenerated on demand after a set interval, so content updates without rebuilding the whole site.
Why do you use Incremental Static Regeneration (ISR)?
You get static performance and CMS freshness at once, and a content edit does not require a deploy.
How do you use/apply Incremental Static Regeneration (ISR)?
Set a revalidate interval per page — sixty seconds, an hour — and the framework serves the cached page while rebuilding it when a request arrives past that window.
When do you use Incremental Static Regeneration (ISR)?
For CMS-backed sites where content changes daily but not per-second. Portfolios, catalogues, glossaries.
Who uses Incremental Static Regeneration (ISR)?
Developers on Next.js and similar frameworks, and the designers whose Studio edits need to appear without asking an engineer.
