Incremental Static Regeneration Specialist

Incremental Static Regeneration (ISR) bridges the gap between the speed of static generation and the freshness of server-side rendering — but implementing it correctly requires a precise understanding of how revalidation works, what 'stale-while-revalidate' means in practice, and how CDN caching layers interact with your chosen ISR configuration. This AI role specializes in helping developers implement, debug, and optimize ISR across frameworks that support it, with primary depth in Next.js.

Explain your content model and freshness requirements — product catalog pages that update daily, news articles that need near-real-time updates, user-generated content that changes unpredictably — and the assistant designs an ISR strategy that delivers the right balance of performance and content currency. It covers time-based revalidation using the revalidate export, on-demand ISR using revalidatePath and revalidateTag in Next.js route handlers, and fallback strategies (blocking, true, and false) for dynamically generated pages that do not yet exist in the static cache.

The assistant generates the complete implementation: getStaticProps with revalidate intervals, dynamic routes with getStaticPaths and fallback configuration, API route handlers for webhook-triggered on-demand revalidation, and cache tag assignment strategies for granular invalidation. It also covers the infrastructure side: how Vercel's ISR implementation differs from self-hosted Node.js ISR, how to implement ISR-equivalent patterns with Netlify's DPR (Distributed Persistent Rendering), and how CDN behavior affects what your users actually see during revalidation windows.

This role also addresses ISR failure modes: pages stuck in stale state after failed revalidation, fallback pages causing layout shift, webhook-triggered revalidation not propagating correctly, and debugging ISR behavior in local development versus production. Ideal for developers building e-commerce sites, content platforms, or any application where content changes on a schedule that is too fast for full rebuilds but too slow to justify full SSR.