Question 1

Are the components accessible?

Accepted Answer

Yes. The shared UI in @workspace/ui is built on Radix primitives, so components come with keyboard support, focus states, and proper ARIA roles out of the box.

Question 2

How do I add a new block?

Accepted Answer

Create it in packages/sanity-blocks/src/, run pnpm type, add its GROQ fragment, and register it in the page builder. The README lists the exact steps.

Question 3

Can I customize the components?

Accepted Answer

Yes. They use Tailwind v4 with CVA variants, and the theme tokens live in globals.css. Edit the tokens to restyle everything, or tweak a single component's variants.

Question 4

How do I update types after a schema change?

Accepted Answer

Run pnpm extract, then pnpm type. That regenerates the Sanity types your components rely on.

Question 5

Where do shared UI components live?

Accepted Answer

Shared primitives live in the packages/ui workspace package (@workspace/ui) and follow the shadcn pattern: Radix primitives for behaviour, CVA for variants, Tailwind v4 for styling. Import them anywhere in the monorepo without copying files between apps.

Page-builder sections are separate: headless block components ship from @workspace/sanity-blocks, and the styled implementations you actually render live in apps/web/src/components/sections. Keep generic buttons and inputs in @workspace/ui, and keep anything Sanity-shaped in the sections folder.

Question 6

What environment variables do I need?

Accepted Answer

The web app needs your Sanity project ID, dataset, API version, Studio URL, and read/write tokens. The Studio needs its matching SANITY_STUDIO_* values. All are validated at startup.

Question 7

How do I deploy?

Accepted Answer

Deploy the Next.js app to Vercel with the root set to apps/web, and deploy the Studio with npx sanity deploy from apps/studio.

Question 8

Why do I need to set CORS origins?

Accepted Answer

Sanity blocks unknown origins, so add your production and preview URLs under API > CORS origins in sanity.io/manage. Enable "Allow credentials" for live preview.

Question 9

Does it work with Vercel previews?

Accepted Answer

Yes. Preview deployments work as long as their URL is allowed in Sanity's CORS settings, and a wildcard origin covers them all.

Question 10

How do I deploy the Studio?

Accepted Answer

The Studio is a normal Vite app in apps/studio, so you have two options. Run npx sanity deploy from that folder to host it for free on a yourproject.sanity.studio subdomain, or deploy apps/studio as its own Vercel project alongside the web app if you want it on your own domain. Whichever you pick, set the studio env vars (SANITY_STUDIO_PROJECT_ID, SANITY_STUDIO_DATASET, SANITY_STUDIO_PRESENTATION_URL) for that environment, and point NEXT_PUBLIC_SANITY_STUDIO_URL on the web app at the deployed Studio so edit links and Presentation resolve correctly.

Question 11

How does live preview work?

Accepted Answer

The Studio's Presentation tool shows your live site next to the editor. Click any element to jump to its field, and edits appear instantly without refreshing.

Question 12

Can editors build pages themselves?

Accepted Answer

Yes. Pages are assembled from reusable blocks like hero, FAQ, and CTA. Editors add, reorder, and edit them in the Studio with no code.

Question 13

Can pages be read as Markdown?

Accepted Answer

Yes. Add .md to any URL (like /about.md) or send an Accept: text/markdown header to get a clean Markdown version, which is handy for LLMs and agents.

Question 14

Does it support multiple languages?

Accepted Answer

Not out of the box. You can add localization with a plugin like @sanity/document-internationalization, but it isn't built in.

Question 15

What happens to old URLs when I change a page slug?

Accepted Answer

Nothing breaks silently, but the old URL will 404 until you add a redirect. The starter ships a redirect document type in the Studio: create one with the old path as the source, the new path as the destination, and choose whether it is permanent (308) or temporary (307). Redirects are content, not code, so editors can add them without a deploy. That keeps SEO intact when marketing restructures the nested page hierarchy.

Question 16

Is it free?

Accepted Answer

Yes. The template is free and open-source under the MIT license. You only pay for the services you host it on.

Question 17

Do I need a paid Sanity plan?

Accepted Answer

No. You can start on Sanity's free tier and upgrade later if your traffic or team grows.

Question 18

What does hosting cost?

Accepted Answer

It depends on your providers. A common setup runs on Vercel and Sanity, both of which have free tiers for small projects.

Question 19

Can I use it for client work?

Accepted Answer

Yes. The MIT license allows commercial use, and Roboto Studio uses this same template in production client projects.

Question 20

Are there any paid dependencies in the stack?

Accepted Answer

No. Every package in the monorepo is open source and free to use: Next.js, React, Sanity Studio, Tailwind v4, Radix UI, Turborepo, and Biome. There is no licence key, no seat charge, and nothing phones home. The only things that can cost money are the services you choose to run it on: your Sanity plan once you outgrow the free tier, and your hosting provider such as Vercel. Clone the repo, run pnpm dev, and you are working locally at zero cost.

Why are we unique

Bleeding Edge

Simplified

Pre-populated

Join our community

Have questions?

Are the components accessible?

How do I add a new block?

Can I customize the components?

How do I update types after a schema change?

Where do shared UI components live?

Production-grade foundations, Enterprise-ready.

Why are we unique

Bleeding Edge

Simplified

Pre-populated

Join our community

Have questions?

Are the components accessible?

How do I add a new block?

Can I customize the components?

How do I update types after a schema change?

Where do shared UI components live?

Subscribe to our newsletter

Production-grade foundations, Enterprise-ready.