Gatsby ISR and Plugin Cache Invalidation: Choosing a Zero‑Downtime Update Strategy

Ensuring data freshness with Gatsby ISR during zero‑downtime migration

Goal: update content in a small Gatsby site using Incremental Static Generation (ISR) so that only changed pages regenerate while the site remains served.

Constraint: ISR regenerates HTML only; data source plugins continue to serve cached data unless they implement incremental fetching, and the documentation does not define a standard method for plugin‑level cache invalidation.

Uncertainty: developers must decide whether to accept occasional stale data, trigger full rebuilds, or implement custom webhook or plugin hooks to refresh data.

• What strategies exist for plugin‑level cache invalidation that work with ISR without causing full rebuilds?
• How can a custom webhook be configured to signal plugins to purge their caches while keeping ISR active?
• Are there any plugin‑specific options or conventions that safely enable incremental data fetching alongside ISR?