What Is Editable In Tina
Files: src/content/, src/config/, src/i18n/, tina/ · Skill level: Beginner
Keep npm run dev running, open http://localhost:4321/admin/, and click Enter Edit Mode. You need no account and no password. Open the menu at the top left, then pick an entry, a language folder, and a file. Tina has the full guide. Everything below exists in English, French, and Arabic, and an edit changes one language.
Give a page about five seconds after it opens, because a page with many sections loads a form for each one. Saving a large form, such as a homepage, can take up to half a minute, so wait for it to finish before you leave the page.
Where Each Page Is Edited
The last column lists the blocks in the page’s own form. Fill one in to change that section on this page only. Every other section comes from Section defaults.
| Address | Entry in /admin/ | The page’s own blocks and fields |
|---|---|---|
/ | Home pages, file -index | Hero, Metrics, Feature Grid, Causes, Reviews, Gift Split, Related Posts, Events, Involved, Clients, Cta |
/home-appeal/ | Home pages, file home-appeal | Announcement Bar, Hero, Appeal Brief, Appeal Updates, Gift Split, Clients, Reviews, Questions, Cta |
/home-community/ | Home pages, file home-community | Hero, Feature Grid, Events, Volunteer Roles, Metrics, Gallery, Plans, Reviews, Newsletter, Cta |
/causes/ | Causes, the listing page | Page Header, Causes, Questions, Cta, and Categories (the cause categories and their filter) |
/causes/{slug}/ | Causes, one file per cause | Goal, Raised, Donors, Deadline, Category, Gallery, Impact, Updates, and the blocks Cause Hero, Questions, Cta |
/donate/ | Donate page and giving data | Currency, Amounts, Default, Minimum, Frequencies, Cover Fees Percent, Impact Map, Tiers, Form, and the blocks Page Header, Jump Nav, Donate, Plans, Spend Split, Other Ways, Questions, Cta |
/events/ | Events, the listing page | Page Header, Event Listing, Cta, and Categories |
/events/{slug}/ | Events, one file per event | Start, End, Timezone, Venue, Address, Online, Capacity, Price, Register Url, and the blocks Event Hero, Cta |
/impact/ | Impact page | Page Header, Figures, Spend, Results, Reports, Facts, Policies, Questions, Cta |
/about/ | About page | Page Header, Story, Values, Steps, Metrics, Team Grid, Clients, Cta |
/team/ | Team, the listing page. Team also has one file per member | Page Header, Jump Nav, Team Grid, Cta |
/gallery/ | Gallery page | Page Header, Cta, and Categories, Items, and Credit for the photos |
/careers/ | Careers, the listing page | Page Header, Open Roles, Values, Steps, Notes, Cta, and Departments |
/careers/{slug}/ | Careers, one file per job | Cta |
/blog/ | Blog listing page | Page Header, Blog List, Newsletter, Related Posts, Story Article, Cta |
/blog/{slug}/ | Blog posts, one file per story | Newsletter, Related Posts |
/blog/category/..., /blog/tag/..., /blog/page/... | Built from the stories | None |
/faq/ | FAQ page | Page Header, Questions, Cta |
/contact/ | Contact page | Page Header, Contact Options, Contact, Questions, Cta |
/volunteer/ | Other pages, file volunteer | Page Header, Feature Grid, Volunteer Roles, Steps, Volunteer, Questions, Cta |
/fundraise/ | Other pages, file fundraise | Page Header, Feature Grid, Steps, Fundraisers, Toolkit, Contact, Questions, Cta |
/tribute/ | Other pages, file tribute | Page Header, Tribute Page, Donate, Questions, Cta |
/partners/ | Other pages, file partners | Page Header, Partners Page, Cta |
/testimonials/ | Other pages, file testimonials. The quotes are in Reviews | Page Header, Video, Reviews, Cta |
/donate/thanks/ | Other pages, file donate-thanks | Donate Thanks |
/elements/ | Other pages, file elements | Page Header, Layout Gallery, Cta |
| Legal pages | Other pages, one file per page | Page Header, Content Page, and the body |
/components/ | Components page. Its body is edited as source code | None |
/events/<slug>.ics | Built from the event’s date, time, and place | None |
| 404 | The Not found section in Section defaults, and Interface labels | None |
The form of Other pages lists every block those pages can use. A block only works on a page that shows that section.
Most page forms also have Main button on this page, Header layout, Footer layout, Robots, Leave out of the sitemap, Leave out of llms.txt and Markdown copies, and Draft.
New Entries
Use Create New in Causes, Events, Careers, Team, Blog posts, Reviews, Authors, and Other pages. The header menu doesn’t pick up a new cause, so add its link to the Causes mega menu in Menus and footer columns, in every language. See Menus.
A new cause needs a Category that is one of the ids in Categories on the Causes listing page. Keep ids as lowercase words, as in the samples: they link things together and don’t show as text. 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
Section defaults holds the shared content of each section, 36 files in all, in each language. A change there shows on every page that uses the section, unless the page has filled in its own block.
| Section | Where it appears |
|---|---|
| Announcement bar | Above the header. It ships off, and /home-appeal/ turns it on in its own block |
| Appeal brief section, Appeal updates section | /home-appeal/ |
| Blog list section | /blog/, its pages, and category and tag pages |
| Call to action | Above the footer on most pages |
| Cause hero section | Cause pages |
| Causes section | /, /causes/, and the related causes on cause pages |
| Clients | /, /home-appeal/, /about/ |
| Contact options section | /contact/ |
| Contact section | /contact/, /fundraise/ |
| Cookie consent | The cookie banner on every page |
| Donate section | /donate/, /tribute/ |
| Event hero section | Event 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 section | All three homepages |
| Metrics section | /, /home-community/, /about/ |
| Newsletter section | /home-community/, blog list pages, and stories |
| Not found section | 404 pages |
| Open roles section | /careers/ |
| Plans section | /donate/, /home-community/. The tiers come from Donate page and giving data |
| Questions section | Most pages, including /faq/, /contact/, /donate/, /causes/, cause pages, and /impact/ |
| Related posts section | /, and under each story |
| Reviews section | All 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. See Section Layouts.
Site-Wide Content
| Entry | What’s in it |
|---|---|
| Site settings | Site (title, tagline, Base Url, logo), Organization (name, registration number, phone, email, address, office hours, time zone), Seo (robots.txt, AI files, sitemap), Settings, Opengraph, and Head for analytics tags |
| Menus and footer columns | Header Primary (dropdowns, flyouts, and the Causes mega menu) and Footer, in menu.en, menu.fr, and menu.ar. The mega menu card names a cause by its file name in Cause. See Menus |
| Social links | Your social profiles |
| Interface labels | Buttons, form messages, footer copy, and counted labels (“1 donor”, “412 donors”), per language. The page-title tagline is seo.tagline here |
Givo has three header layouts and three footer layouts. Choose them in Site settings > Settings > Layout, or per page with Header layout and Footer layout. Settings also holds 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.
If You Clear A Field
In a page’s form, a field you never filled uses the default. A field you clear is saved empty, which hides that text or image on that page.
Tina can’t bring the default back by itself. To get the text back, do either of these:
- Copy it from Section defaults into the field.
- Remove the empty line from the page’s file in
src/content/with a text editor.
Money In Every Language
Each cause holds its own goal, amount raised, donors, and deadline. The currency, preset amounts, monthly tiers, and impact map are under Donate page and giving data. These numbers must be the same in every language, so change an amount in each language’s file. npm run build prints a [donate] warning that lists any that differ. Currency is a three-letter code (USD, EUR), not a symbol.
“Days left”, “Last day”, and “Ended” are worked out when the site builds, from each cause’s Deadline. See Causes & Campaign Progress.
What The Preview Doesn’t Update
The header, the menus, and values from Site settings, such as contact details, don’t change while you type. They update when you save. Some Site settings also need npm run dev restarted, and the note on the field says so.
These have no click-to-edit outline, so change them in their forms: the header and menus, values from Site settings, images with no alt field, categories and tags, and one-word options. Online with Tina Cloud there are forms only.
When Tina saves, it removes comments and rewrites Markdown in its own style, such as * in place of -. Your words and values stay, and the comments’ text is kept as the note under each field. If you also edit content files by hand, run npm run tina:audit. It tells you if a save would lose anything.
In stories and legal pages, keep [.h5] at the end of a heading (it is a size setting), and leave {name}, {phone}, {email}, {address}, and {hours} as they are: they are filled in from Site settings > Organization.
What Stays In Code
- Which sections a page has, and their order: the route in
src/pages/[...lang]/. You can hide a section with its Enable field. - New sections, new page routes, and new layouts. Then run
npm run tina:generateso the editor offers them. - The money and progress rules (
src/lib/campaign.ts,src/lib/causes.ts,src/lib/donate.ts): how progress, days left, and “Ended” are worked out. The figures they read are editable. - Colors and type scale (
src/styles/theme.css), fonts (src/config/fonts.json), and the heart mark (src/lib/brandMark.ts). - The list of languages. See Internationalization. After you add one, run
npm run tina:generateand restartnpm run dev. - The icons themselves. Icon names are text you can edit.
Versions And Testing
This edition is tested on Astro 7.4.12 and Node 22, with tinacms 3.15.1, @tinacms/cli 4.0.4, and @tinacms/astro 0.8.0. They are pinned in package.json. The live preview uses experimental features of @tinacms/astro, so test it before you upgrade. Node must be 22 (22.12 or later) or 24.
We saved every content and settings file through the editor and checked that nothing was lost, saved an Arabic page at /admin/, and checked that the live preview shows the same page as the built site on all 197 page addresses in the three languages. We have not run online editing against a live Tina Cloud project. Try one save on a copy of your site before you rely on it.
Do It With AI
I use the Tina edition of Givo. Tell me where to edit [TEXT OR SETTING] in /admin/: the entry, thelanguage folder, the file, and the field. If it comes from Section defaults, say which pages willchange, and how to change it on one page only. Don't change any files.