Manage Sanity with code
Blueprints let you have infrastructure-as-code level management for your Sanity resources.
Introduction
Learn what Blueprints are, how they work, and how to get started.
Your first Blueprint
Set up a blueprint, run a plan, and deploy your first resource (a CORS origin) to a real Sanity stack.
Create a Sanity Function
Use Blueprints to create a function
Deploy Blueprints with GitHub Actions
Use the official Blueprints actions to plan and deploy your Blueprints with GitHub Actions.
Stacks and scope
How one blueprint file maps to many stacks, and what project versus organization scope means.
The resource graph
How resources reference each other with the $ syntax, and why a blueprint file is a connected system.
Manage environments with Blueprints
Deploy one blueprint file to staging, production, and other stacks.
Errors and rollbacks
How Blueprints catches mistakes early and what happens when a deploy fails.
Configuration reference
Reference documentation for the Blueprint configuration files.
Blueprints CLI command reference
Reference documentation for the Sanity CLI Blueprints command.
Blueprints scopes reference
Project versus organization scope, which resource types need which scope, and how the CLI resolves scope.
Blueprints glossary
Definitions of the core Blueprints terms: stacks, scopes, values, deletion policies, and more.