Sanity development
Sanity Studio, set up the way your editors work.
Sanity can be shaped to fit almost any content workflow. That flexibility means small changes — a new schema, a custom input, a fixed preview — need a developer who knows it.
The problem
Sanity projects are code-configured, so editors depend on a developer for every change to the Studio. Upgrades between Studio versions and changes to queries can also break the front end quietly.
We make schema and Studio changes in your repository, migrate existing content with scripts where needed and test the front end against the result before deploying.
Sound familiar?
- Editors need a new document type, field or custom input.
- Visual Editing or draft preview is not working.
- An older Studio needs upgrading to the current version.
- Existing content needs restructuring to fit a new schema.
- A GROQ query is slow or returning the wrong content.
What you get
- Schema and Studio changes committed to your repository
- Content migration scripts, run on a test dataset first
- Front-end query and component updates to match
- A short note for editors on what changed
What this isn’t
- Full site builds or CMS migrations (quoted separately or referred)
- Large custom Studio plugins or apps
- Ongoing content entry
Timeframe
Most jobs take 2–7 business days. Studio upgrades usually 1–2 weeks.
Technologies
How the job runs
- 01
Describe what is stuck
Answer a few questions in the scoping agent. It takes about three minutes and turns your answers into a plain-English brief.
- 02
Get a straight answer
Within one business day, a developer replies with a fixed price, a paid diagnostic, one question, or an honest “not us” and a referral.
- 03
We fix it
Work starts when you approve. You get the fix, a short note on what changed and the access handed back.
Scoping agent
Tell us what’s stuck.
Two minutes of guided questions. You get a plain-English brief, and a developer replies within one business day.
- Guided questions, not an AI chatbot
- A person reviews every brief
- Never asks for passwords or keys
No account. No sales script. Never asks for passwords or keys.
Questions
Will migrating content lose anything?
We run migrations on a copy of your dataset first and check the result before touching production content.
Can you upgrade an older Studio?
Usually, yes. We check custom plugins and inputs first and tell you if any need rewriting before quoting.
How do we give you access?
Invite us to the Sanity project and repository with the role needed, and remove access when we finish.