We're currently using Static Site Generation (SSG) with Incremental Static Regeneration (ISR), which causes Next to generate every page server-side and then update them after a revalidate period (60 seconds on deployed website) if there is new content for them (e.g., images; text changes; etc.). While great for performance, this causes a lag is showing edits on Airtable on the actual website.
We can switch to using Server-Side Rendering (SSR) which renders each page on request. With this approach, the data will always be up-to-date when the page is loaded (or reloaded), but will take a second or two to compile the website on each request. For our purposes, this is probably fine.
We're currently using Static Site Generation (SSG) with Incremental Static Regeneration (ISR), which causes Next to generate every page server-side and then update them after a
revalidateperiod (60 seconds on deployed website) if there is new content for them (e.g., images; text changes; etc.). While great for performance, this causes a lag is showing edits on Airtable on the actual website.We can switch to using Server-Side Rendering (SSR) which renders each page on request. With this approach, the data will always be up-to-date when the page is loaded (or reloaded), but will take a second or two to compile the website on each request. For our purposes, this is probably fine.