Connect a website

Connect a Sanity website

Deploy the schema, create a token, connect.

For a Sanity website, nothing changes in the site's code. SiteHome works with one API token and the schema your Studio deploys.

1. Deploy the schema

SiteHome reads which fields exist from the schema Sanity stores when your Studio is deployed. If the Studio is not hosted by Sanity, deploy the schema yourself after each schema change:

npx sanity schema deploy

2. Create a token

In Sanity Manage, open the project, go to API → Tokens, choose Add API token, name it SiteHome and pick the Editor role (with Viewer, SiteHome can show content but not publish). Copy the token.

3. Connect in SiteHome

In the SiteHome app: Connect website → Sanity, paste the token, confirm the website address, choose the dataset and the content types. Publishing starts switched off until an administrator switches it on. A dataset that is already connected in SiteHome is never taken over; its administrator invites you.

How SiteHome publishes

Every change is reviewed first. SiteHome writes a draft and publishes it through Sanity's Actions API with a revision check, so it never overwrites someone else's newer change or another person's draft. Taking an item off the website uses Sanity's unpublish action; the item stays recoverable as a draft.

What SiteHome edits

Fields from your deployed schema, by one rule: fields without a rule of your own are editable; fields with a custom validation rule, or shown only under a condition, stay read-only with a neutral explanation. Text, numbers, booleans, dates, choices, slugs of new items, images (with alt text), lists, Portable Text and arrays of simple objects are supported.