🦙Tina - Add ISR for content changes

[Calinator444]

CC: @wicksipedia, @miichaelsmedley

The Pain

Changes made using Tina cannot be previewed (outside of the Tina editor). Until the branch has been re-deployed. This can result in confusion.

Solution

We should investigate using ISR so that static routes using Tina are rebuilt when data is updated in Tina Cloud

Option 1: Use on-demand webhooks to invalidate the cache after saving

Note: Tina may not have webhook support yes, discuss this with Wicksy/someone from the Tina team
https://vercel.com/templates/next.js/on-demand-incremental-static-regeneration
https://nextjs.org/docs/app/building-your-application/data-fetching/incremental-static-regeneration#on-demand-revalidation-with-revalidatepath

Option 2: Time based revalidation (not recommended)

https://nextjs.org/docs/app/building-your-application/data-fetching/incremental-static-regeneration#time-based-revalidation

Figure: outdated page being shown while staging branch rebuilds

[wicksipedia]

Time based revalidation could be used as an interim measure. This is useful for content that doesn't update often.

For content that is revised more frequently - we are planning on adding webhook support to TinaCloud so that you can get a webhook when content is updated. This would include the list of files that changed, and the routes that changed (as based on the Tina config).

This used in conjunction with https://nextjs.org/docs/app/building-your-application/data-fetching/incremental-static-regeneration#on-demand-revalidation-with-revalidatepath would allow you to use ISR effectively.