
Grab your gear: The official Sanity swag store
Read Grab your gear: The official Sanity swag storeI can see you're having an issue with a template not being on the main branch, but your question doesn't include enough context for me to give you a specific answer. However, this is a common issue with Sanity templates and GitHub repositories, so let me cover the most likely scenarios:
Common Causes & Solutions:
Template Branch Structure: Many Sanity templates and starter projects use different branch structures. Some templates have their working code on a studio-v3 branch, v3 branch, or other feature branches rather than main. Check the repository's README or GitHub branches dropdown to see what branches exist.
Template Installation Method: If you're using npm create sanity@latest or similar CLI commands, the template should automatically pull from the correct branch. If you're manually cloning from GitHub, make sure you're:
main)Outdated Template References: Some older templates or documentation might reference branches that have since been merged or renamed. Look for:
What to do:
git clone -b <branch-name> if you know the correct branch namenpm create sanity@latest) is usually more reliable than manual cloningIf you can share which specific template you're working with (a GitHub URL or template name), the community can give you more targeted help!
Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.
Content operations
Content backend


The only platform powering content operations
By Industry


Tecovas strengthens their customer connections
Build and Share

Grab your gear: The official Sanity swag store
Read Grab your gear: The official Sanity swag store