Hello, I have an important question regarding something I noticed while building a website using Prismic with Next.js.
When I create a new page from the Prismic dashboard and click "publish," I find that the page appears on the site without any deployment or without using the live preview feature.
Is this behavior normal, or is there a problem that I might be missing?
Hey team!If changes are published immediately, that's actually a good sign—it likely means your project setup is optimized for fast updates.
When webhooks and automatic builds are set up correctly, content can be displayed right away after you publish documents in your repository. Is this the behavior you were expecting?
Thank you for your response, @Pau. I wasn’t expecting that. This is the default setup; I haven’t done anything additional to make it work. I assumed that for new content to appear on my production website, I would need to configure a webhook to listen for each publication on the Prismic dashboard to trigger a build or perform it manually.
My question is: if I leave it as it is, will every publication on Prismic reflect directly on my website without requiring builds or deployments? Is this correct, and are there no potential side effects on SSR or anything else?
One more thing: I’d like to understand how this works. How does my website recognize the latest updates from Prismic and render them, even for pages that didn’t exist before and would typically require a build to resolve their routes and handle redirects?
We're hosting the site on Vercel with Next.js 14, and most of our components are server-side, fetching data through Prismic. We haven't linked any webhooks to the deployment yet, but it still works, which was surprising to me. It updates new content without a full rebuild, which is really cool!
Do you recommend any best practices or concerns I should keep in mind while having ISR?
Hey Ahmad, even though webhooks can tell you when a change is triggered, they can't actually perform rebuilds on the live site. This action has to be handled outside of Prismic within your deployment platform.