Question 1

Are the components accessible?

Accepted Answer

Yes. The shared components in @workspace/ui wrap Base UI primitives, so keyboard navigation, focus management, and ARIA roles come built in.

Question 2

How do I add a new block?

Accepted Answer

Add a folder under packages/sanity-blocks/src/ and export its schema from blockSchemas — the Studio picks it up automatically. Run pnpm type, add the projection to pageBuilderFragment, then register the component in renderBlockComponent.

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 type from the repo root — it regenerates packages/sanity/src/sanity.types.ts. To refresh the schema snapshot first, run pnpm extract inside apps/studio.

Question 5

Where do shared UI components live?

Accepted Answer

Generic primitives like buttons and inputs live in @workspace/ui. Page-builder blocks live in packages/sanity-blocks/src/<block>/index.tsx and are rendered by apps/web/src/components/pagebuilder.tsx.

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 — all Zod-validated by @workspace/env at startup. The Studio reads its own SANITY_STUDIO_* values; see the .env.example in each app.

Question 7

How do I deploy?

Accepted Answer

Deploy the web app to Vercel with the root directory set to apps/web. For the Studio, run pnpm run deploy from apps/studio — not pnpm deploy, which is pnpm's own command.

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, as long as the preview URL is added to your Sanity CORS origins under API > CORS origins in Sanity Manage.

Question 10

How do I deploy the Studio?

Accepted Answer

Run pnpm run deploy from apps/studio. The first deploy has to run locally so Sanity can create the hosted Studio and return an app ID — save it as SANITY_STUDIO_APP_ID for later deploys.

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

No. This starter has no localization set up — every document type is single-language.

Question 15

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

Accepted Answer

When a page's slug changes, the auto-redirect Sanity Function creates a redirect document pointing the old path at the new one. Next.js reads those in next.config.ts, so the redirect goes live on the next build.

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. It's MIT licensed, so commercial and client work are both fine.

Question 20

Are there any paid dependencies in the stack?

Accepted Answer

No. Everything in the stack is open source — Next.js, Sanity Studio, Tailwind v4, Base UI, Turborepo, and Biome. You only pay for the services you host on, such as Sanity and Vercel.

Build websites as fast as hell

Why are we unique

Bleeding Edge

Simplified

Pre-populated

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.

Build websites as fast as hell

Why are we unique

Bleeding Edge

Simplified

Pre-populated

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.