Incremental Static Generation

Static Generation (SSG) addresses most of the concerns of SSR and CSR but is suitable for rendering mostly static content. It poses limitations when the content to be rendered is dynamic or changing frequently.

Think of a growing blog with multiple posts. You wouldn't possibly want to rebuild and redeploy the site just because you want to correct a typo in one of the posts. Similarly, one new blog post should also not require a rebuild for all the existing pages. Thus, SSG on its own is not enough for rendering large websites or applications.

When to Use

• Use this when you have mostly static pages that need periodic data updates without full rebuilds
• This is helpful for large sites (blogs, e-commerce) where rebuilding every page on each change is impractical

When NOT to Use

• When content changes in real-time and stale data is unacceptable (e.g., live scores, stock tickers)
• For pages that are fully dynamic and personalized per user — SSR is a better fit
• When the revalidation window creates a confusing experience where different users see different content versions

Instructions