sanity-best-practices

Stack optimizable filters like _type and defined() first so indexes reduce the search space, use _ref instead of -> in filters, and always project only needed fields. For deep pagination, use cursor-based queries with _id rather than large slice offsets.

Use defineLive from next-sanity/live and fetch data via sanityFetch instead of scattering raw client.fetch calls. Wrap queries in defineQuery so TypeGen generates result types automatically, and configure the Presentation tool for Visual Editing.

Angular has no official Visual Editing support — there is no Stega encoding or click-to-edit overlay integration. You can build a basic preview mode with a token-authenticated client using the drafts perspective, kept server-side only.

TypeGen generates TypeScript types from your schema and GROQ queries. Enable it in sanity.cli.ts with a path glob and output file, wrap queries in defineQuery, and types regenerate during sanity dev or via npm run typegen.

Use Sanity Functions when you need to read or mutate document data in response to content events, such as setting computed fields or calling Agent Actions. Use a plain webhook when you only need to notify an external URL on publish without data shaping.

The function mutates the same document type it listens to, creating an infinite loop. Add a GROQ filter that excludes already-processed documents, such as !defined(firstPublished), and use @sanity/client v7.12.0+ for automatic lineage-based recursion protection.