Improving Content Publisher Site Performance
This document provides guidelines you can follow to help improve the performance of your sites using Content Publisher.
If your site’s pages do not require fetching content from Content Publisher dynamically, you should consider statically generating the pages on your site.
If you’re on our default starter kits for example, your site performs on-demand server side rendering of pages – data is fetched from on every page load and used to render the page. This is overhead you might not need if your content does not change often or you do not show personalized content to different users.
Static Site Generation (SSG) as it is called in frameworks like Next.js and Nuxt allows you to pre-render pages in your site, cache the built HTML files on a CDN and serve them to users as fast as possible.
Content Publisher starter kit supports SSG by allowing you to fetch the data for rendering your pages at build time and importantly, offering webhooks for content invalidation.
Content invalidation webhooks are important because after your site is built and deployed, published changes to content in Content Publisher should be reflected on these pages. Content Publisher lets your site know when it should rebuild pages with the updated content using these webhooks.
You can find an example of building pages statically in our example starter kit, and the Setup Content Cloud Invalidation On Static Sites document details setting up content invalidation with Content Publisher webhooks.