Example, using SSG with revalidate option
This page will always be rendered statically, but the static bundle may be built either when deploying the website (AKA "pre-built"), or on-demand.
When it is built "on-demand", the existing static version gets displayed to the end-user immediately, and a rebuild is performed in the background.
The next user who load this page will get the newer static version.
The max age of this page has been set to 30 seconds.
By using incremental static regeneration, this page is kept up-to-date automatically, based on how often users open the page.
Of course, a few users will see outdated information, but it's not really an issue here.
If you use Stacker and update the products there, then when you refresh the page (once the delay of 30 seconds has passed) then the whole page will be statically regenerated.
And then, you'll have to refresh once again to see the new static version.
When it is built "on-demand", the existing static version gets displayed to the end-user immediately, and a rebuild is performed in the background.
The next user who load this page will get the newer static version.
The max age of this page has been set to 30 seconds.
By using incremental static regeneration, this page is kept up-to-date automatically, based on how often users open the page.
Of course, a few users will see outdated information, but it's not really an issue here.
If you use Stacker and update the products there, then when you refresh the page (once the delay of 30 seconds has passed) then the whole page will be statically regenerated.
And then, you'll have to refresh once again to see the new static version.
In development mode and when the preview mode is enabled on staging, it is not possible to simulate
Each page refresh will completely refresh the page, any previous build will be ignored, and
revalidate mode properly.Each page refresh will completely refresh the page, any previous build will be ignored, and
builtAt will be reset.Published products
Draft products
sdfghnjsdfghj
sdfgh
0€