What Is Editable In Sanity

What Is Editable In Sanity

Files: sanity.config.ts, sanity/, src/config/config.toml · Skill level: Beginner

Run npm run dev:all, open the Studio at http://localhost:3333, and log in with your Sanity account. Content has one entry per language, then Site settings. Sanity has the full guide, including npm run setup for your first project. Everything below exists in English, French, and Arabic, and each language has its own documents.

Where Each Page Is Edited

All locations are under Content, then your language. The last column lists the rows you can add under Sections on this page. Each row changes one section for this page only, and a field you leave empty keeps the section’s own content.

On Areas, Projects, Jobs, Industries, and Reviews, this list also holds parts of the entry that aren’t sections, such as Hours or Reply.

Homio’s Studio has no Page options group. Each document’s page fields sit with its other fields: Meta Title and Meta Description on most pages, Draft on most documents (not the homepages), and on Other pages and the three extra homepages, Robots and Exclude From Sitemap. Exclude From AI is only on Other pages. Header Layout is only on those three homepages, and Footer Layout is on those homepages and Other pages.

New Entries

Use the + button in Services, Areas, Industries, Projects, Reviews, Blog posts, Authors, Team members, Jobs, and Other pages. The header menu doesn’t pick up a new service or area, so add its link in Menus. See Menus.

A new entry with only a title won’t break the site, and it builds. Its card or page shows what you filled in, and images and other fields stay empty until you add them, so fill them in before you publish. We tested this in the bundled demo content, not on a real project.

Sections

Each section is one document per language, under Sections. Open its Section content row to edit it. Every page that shows it uses this content, unless the page changes it under Sections on this page.

To hide a section, use its Enable field. To change its look, use Options > Layout. /elements/ previews every layout, and its notes still name the file paths of the Astro edition.

Site-Wide Content

Settings holds the header and footer layouts (Layout), Navigation Button, Mobile Action Bar, Copyright, Subscription, Theme Credit, Page Actions, Smooth Scroll, Color Scheme, Cookie Consent, Estimator, Booking, Contact Form Action, and Contact Form Provider.

Site settings apply when the site builds. While npm run dev:all runs, they apply when you publish them, and the page reloads. They don’t change as you type, and click-to-edit doesn’t reach them, so change them in their form. Click-to-edit also doesn’t reach option values, links, icon names, hours, interface labels, or images set as a CSS background.

Plans And Attributes

At the time of writing, Sanity’s free plan allows 2,000 attributes, one for each distinct field path in your content. Homio’s demo content, with its images, measured 1,681 in our test project, read from Sanity’s own count after importing it and using Live preview. It fits, with 319 left.

To stay there, labels are one searchable list, a section’s fields sit in one row, and images have no crop or hotspot option. Adding entries, pages, and text costs nothing. New field names use more, and so do deeper menu levels. You can see your own number in Sanity’s project settings, under Usage. Sanity’s pricing page has the current limits.

Online Preview

Click-to-edit and draft preview work out of the box on your own computer, with npm run dev:all. To use them online, your editors need a second copy of the site running as a small Node.js server, because drafts can’t be shown from static files. A static host can’t do this. See Sanity for the steps. Without a preview server, editors online can still edit in the Studio’s forms and publish.

What We Tested

On this theme: the demo content imported into a real Sanity project, Live preview, and the preview server running on localhost.

Not tested on this theme:

• Any online host, a deployed Studio, or a webhook from end to end.
• Netlify or Vercel functions, which the preview server doesn’t support.
• npm run setup all the way through, importing from the unzipped zip, and adding a language.

Try these on your own project before you rely on them.

What Stays In Code

These change how the site is built, not what it says:

• The page routes and the order of sections on a page: src/pages/[...lang]/.
• Section and component design, colors, type scale, and fonts.
• The list of languages: src/config/language.json.
• Favicons, the language settings, and the collection folder names in config.toml.
• The layout switcher settings, and the list of sections shown on /elements/.
• The AI crawler lists. The on and off switches are in Site settings.
• Which sections and fields exist. To add one, see SKILLS.md.

Do It With AI

I use the Sanity edition. Tell me where to edit [TEXT OR SETTING] in the Studio: the language entry,
the document, and the field. If it comes from a section document, say which pages will change, and
how to change it on one page only. Don't change any files, and don't print anything from .env.