Sanity useCdn true vs false for a read-after-publish content page
We run a Next.js front end backed by Sanity (assume a recent @sanity/client major; exact version semantics to be confirmed against its changelog). One concrete constraint: after an editor publishes an update, the public article page is revalidated and re-fetched within seconds, and readers should not see the pre-publish version. The client exposes the docume
sanity