sanity-best-practices

name

sanity-best-practices

description

Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, event-driven content automation, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity/functions, @sanity/blueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.

Sanity Best Practices

Comprehensive best practices and integration guides for Sanity development, maintained by Sanity. Use the quick reference below to load only the one or two topic files that match the task.

When to Apply

Reference these guidelines when:

• Setting up a new Sanity project or onboarding
• Integrating Sanity with a frontend framework (Next.js, Nuxt, Astro, Remix, SvelteKit, Hydrogen)
• Writing GROQ queries or optimizing performance
• Designing content schemas
• Implementing Visual Editing and live preview
• Working with images, Portable Text, or page builders
• Configuring Sanity Studio structure
• Setting up TypeGen for type safety
• Implementing localization
• Migrating content from other systems
• Building custom apps with the Sanity App SDK
• Managing infrastructure with Blueprints
• Automating content workflows with Sanity Functions or webhooks

Global Rules

• Let Sanity generate _id values for ordinary documents. Do not create deterministic UUIDs, slug-derived IDs, or legacy-system IDs when creating documents.
• Model relationships with fields, then resolve related documents with GROQ lookups, source-key fields, or returned values from created documents.