incremental-static-rendering

Incremental static regeneration updates pre-rendered pages without full rebuilds by revalidating cached outputs over time. You can keep statically generated pages up to date by defining revalidate timing in getStaticProps for stale-while-revalidate behavior.

Lazy page creation generates missing routes on first request to avoid prebuilding everything upfront. You can configure getStaticPaths fallback in Next.js to support on-demand generation of new pages for large sites.

You need incremental static regeneration when data changes periodically and full redeploys are impractical, such as for large blogs or e-commerce sites where new posts or product updates should appear quickly.

Background regeneration revalidates pages on a schedule so users keep seeing a cached version while updates are prepared. Setting a revalidate property in getStaticProps triggers this stale-while-revalidate behavior automatically.

On-demand updates support immediate revalidation after content changes to reduce stale content. This allows you to trigger updates to cached static outputs instantly rather than waiting for the scheduled revalidate interval.

Incremental static regeneration targets e-commerce sites where full redeploys are impractical. By configuring getStaticPaths fallback, you can lazily generate new product pages on demand and revalidate existing ones over time.