With Cache Components you decide, per function, what is cached and for how long. For a content site fed by a CMS that is exactly the control you want.
Cache the data, not the page
I wrap CMS reads in cached functions with tags such as pages, posts and projects. Pages stay fast because they render from cached data.
Refresh on demand
When an editor publishes, the CMS calls a small webhook that revalidates only the tags that changed, so the site updates in seconds without a full rebuild.
Stream what is dynamic
- Wrap anything that reads the request in Suspense.
- Keep the shell static so the first paint is instant.
- Add a loading state only where the data really waits.
The result is a site that feels static to visitors and still updates the moment you hit publish.