Pre-render stragety for CMS content
Hello 
I'm building a site which will potentially have 1000s of pages with content from a CMS. I wish to pre-render these pages, but the content from the CMS can potentially change daily.
I'm thinking a potential approach similar to that of ManniL in his video: https://www.youtube.com/watch?v=Qgsd6-Hsbz4, however I don't want to pre-render all of them on every deploy if only a select few have changed.
My problem is:
Does anyone have a smart solution to selective only pre-render certain pages where content has changed and re-use pre-rendered pages that have not changed?
I'm building a site which will potentially have 1000s of pages with content from a CMS. I wish to pre-render these pages, but the content from the CMS can potentially change daily.
I'm thinking a potential approach similar to that of ManniL in his video: https://www.youtube.com/watch?v=Qgsd6-Hsbz4, however I don't want to pre-render all of them on every deploy if only a select few have changed.
My problem is:
Does anyone have a smart solution to selective only pre-render certain pages where content has changed and re-use pre-rendered pages that have not changed?
YouTubeAlexander Lichter
Nuxt 3 builds are already significantly faster than in Nuxt 2. But they can be even faster, especially if only data or server routes change. In this video, we will explore a module from Pooya, bringing back a "build cache" - and we will dive deep into how it works and why you want to use it.
Key points:
How to improve build time for re-buil...
Nuxt 3 builds are already significantly faster than in Nuxt 2. But they can be even faster, especially if only data or server routes change. In this video, we will explore a module from Pooya, bringing back a "build cache" - and we will dive deep into how it works and why you want to use it.Key points:
How to improve build time for re-buil...
