Skip to content
New: Customize your theme with an AI assistant. Read the guide

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 own 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.

You can look at the site before you have a project: with no .env file, npm run dev and npm run build use the demo content bundled in sanity/seed/demo-content.json.

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.

AddressStudio locationSections on this page rows
/Homepages > Home: CharityHero, Metrics, Feature Grid, Causes, Reviews, Gift Split, Related Posts, Events, Involved, Clients, CTA
/home-appeal/Homepages > Home: AppealAnnouncement Bar, Hero, Appeal Brief, Appeal Updates, Gift Split, Clients, Reviews, Questions, CTA
/home-community/Homepages > Home: CommunityHero, Feature Grid, Events, Volunteer Roles, Metrics, Gallery, Plans, Reviews, Newsletter, CTA
/causes/Main pages > Causes page. The cause categories are fields of this pagePage Header, Causes, Questions, CTA
/causes/{slug}/Causes, one document per cause: goal, raised, donors, deadline, category, photos, impact lines, and updatesNone
/donate/Main pages > Donate page and giving data. The currency, frequencies, cover-fees percent, impact map, and tiers are fields of this pagePage Header, Amounts, Default, Form, Donate, Plans, Spend Split, Other Ways, Questions, CTA
/events/Main pages > Events page. The event categories are fields of this pagePage Header, Event Listing, CTA
/events/{slug}/Events, one document per event: start, end, time zone, venue, address or online, capacity, price, and register linkNone
/impact/Main pages > Impact pagePage Header, Figures, Spend, Results, Reports, Facts, Policies, Questions, CTA
/about/Main pages > About pagePage Header, Story, Values, Steps, Metrics, Team Grid, Clients, CTA
/team/Main pages > Team page, and Team membersPage Header, Team Grid, CTA
/gallery/Main pages > Gallery page. The photos and filter labels are fields of this pagePage Header
/careers/Main pages > Careers pagePage Header, Open Roles, Values, Steps, CTA
/careers/{slug}/Jobs, one document per jobPay only
/blog/Main pages > Stories pagePage Header, Related Posts, Story Article, Newsletter, CTA
/blog/{slug}/Stories, one document per storyNone
/blog/category/..., /blog/tag/..., /blog/page/...Made from StoriesNone
/faq/Main pages > FAQ pagePage Header, Questions, CTA
/contact/Main pages > Contact pagePage Header, Contact Options, Contact, Questions, CTA
/volunteer/, /fundraise/, /tribute/, /partners/, /testimonials/, /donate/thanks/, /elements/, /components/, legal pagesOther pages, one document per page. The quotes on /testimonials/ are in ReviewsThe same list for every page: use the sections that page shows
/events/<slug>.icsMade from each event’s date, time, and placeNone
404Sections > Not found section, and Interface labelsNone

Each document’s page fields sit with its other fields. Draft is on most documents (not the homepages). Robots is on Other pages and the appeal and community homepages, and Header Layout and Footer Layout are on those two homepages. Exclude From AI is only on Other pages.

New Entries

Use the + button in Causes, Events, Stories, Authors, Jobs, Reviews, Team members, and Other pages. The header menu doesn’t pick up a new cause, so add its link to the Causes mega menu in Menus, in every language. See Menus.

A new cause needs a category that is one of the ids in the categories of the Causes page. A new entry with only a title builds. Its card or page shows what you filled in, so fill in the goal, the image, and the rest before you publish.

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.

SectionWhere it appears
Announcement barAbove the header. It ships off, and /home-appeal/ turns it on in its own row
Appeal brief section, Appeal updates section/home-appeal/
Blog list section/blog/, its pages, and category and tag pages
Call to actionAbove the footer on most pages
Cause hero sectionCause pages
Causes section/, /causes/, and the related causes on cause pages
Clients/, /home-appeal/, /about/
Contact options section/contact/
Contact section/contact/, /fundraise/
Cookie consentThe cookie banner on every page
Donate section/donate/, /tribute/
Event hero sectionEvent pages
Event listing section/events/
Events section/, /home-community/
Feature grid section/, /home-community/, /volunteer/, /fundraise/
Fundraisers section, Toolkit section/fundraise/
Gallery section/home-community/
Gift split section/, /home-appeal/, /donate/
Hero sectionAll three homepages
Metrics section/, /home-community/, /about/
Newsletter section/home-community/, blog list pages, and stories
Not found section404 pages
Open roles section/careers/
Plans section/donate/, /home-community/. The tiers come from the Donate page and giving data
Questions sectionMost pages, including /faq/, /contact/, /donate/, /causes/, cause pages, and /impact/
Related posts section/, and under each story
Reviews sectionAll three homepages, /testimonials/
Steps section/about/, /volunteer/, /fundraise/, /careers/
Story section/about/
Team grid section/about/, /team/
Values section/about/, /careers/
Video section/testimonials/
Volunteer roles section/volunteer/, /home-community/
Volunteer section/volunteer/ (the sign-up form)

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

LocationWhat’s in it
MenusHeader menu, with Dropdown items, the Causes mega menu (Mega menu columns, Mega menu card, Mega menu bottom bar), and Footer columns. Set Cause on the card to a cause’s file name, and the card shows that cause’s title, progress, and link. Each language has its own. See Menus
Interface labelsButtons, labels, form messages, counted words (“412 donors”), and the page-title tagline (seo.tagline), as a list of about 360 rows with a search box. Each language has its own
Site settingsOne for the whole site, below the languages: Site, Organization, SEO, Settings, Opengraph, Head for analytics tags, and Social

Settings holds the header and footer layouts (Layout), Patterns, Sticky Header, Navigation Button, Navigation Secondary Link, Mobile Action Bar, Copyright, Subscription, Theme Credit, Page Actions, Smooth Scroll, Animation, Color Scheme, Cookie Consent, 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, ids, hours, interface labels, or images set as a CSS background.

Text in body fields can use {phone}, {email}, {address}, {hours}, and {name}. They show the values from Site settings > Organization.

Money In Every Language

Each cause document holds its own goal, amount raised, donors, and deadline. The currency, preset amounts, monthly tiers, and impact map are in Donate page and giving data. Keep these numbers the same in every language: npm run build prints a [donate] warning that lists any that differ. “Days left”, “Last day”, and “Ended” are worked out when the site builds, so rebuild the site daily while appeals run. See Causes & Campaign Progress.

Numbers In Arabic Text

Body text has a Left to right mark in the editor’s toolbar. Select a number with its unit inside Arabic text and apply the mark, so it keeps its order. It does the same as <bdi dir="ltr"> in the Astro edition. Amounts, phone numbers, and addresses stay left to right by themselves, so they don’t need it.

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. Givo’s demo content, with its images, measured 1,356 in our test project, read from Sanity’s own count after importing it and using Live preview. It fits, with 644 left. You can see your own number in Sanity’s project settings, under Usage.

To stay well under the limit, interface labels are one searchable list, a section’s fields sit in one row, and images have no crop or hotspot option, which would add attributes for each image field. Adding entries, pages, and text costs nothing. New field names use more, and so do deeper menu levels or blocks nested more deeply in a body field. Sanity’s pricing page has the current limits.

Live Preview And Online Preview

The Studio’s Live preview (Sanity’s Presentation tool) shows your site beside the editor. Click text or an image on the page to open its field, and see drafts before you publish. It runs on your own computer with npm run dev:all.

To use it online, your editors need a second copy of the site running as a small Node.js server on a host that can run one, 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, the site built from it and compared with the site built from the bundled demo content, editing in Live preview in English and Arabic, and the Studio schema validated with npm run sanity:validate.

Not tested on this theme:

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

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.
  • How money, progress, days left, and counted words are worked out: src/lib/campaign.ts, src/lib/plural.ts. The currency, amounts, and every label are editable.
  • The list of languages: src/config/language.json.
  • Favicons, the language settings, and the layout switcher settings in config.toml.
  • 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 of Givo. 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.
Type something to search...