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.
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 on the page comes from Section defaults. Almost every form also has a Cta Section block for the call to action above the footer, and Header layout and Footer layout fields, so the table leaves those out.
| Address | Entry in /admin/ | The page’s own blocks |
|---|---|---|
/ | Home pages, file -index | Hero Saas, Clients, Steps, Stack, Platform, Metrics, Customer Quotes, Code Tabs, Feature Grid, Regions, Templates, Plans, Questions, Changelog |
/home-api/ | Home pages, file home-api | Hero Saas, Clients, Feature Grid, Code Tabs, Plans, Customer Quotes, Questions |
/home-ai/ | Home pages, file home-ai | Hero Saas, Clients, Feature Grid, Steps, Customer Quotes, Plans, Questions |
/home-analytics/ | Home pages, file home-analytics | Hero Saas, Clients, Feature Grid, Metrics, Customer Quotes, Plans, Questions |
/about/ | About | About Hero, Story, Values, Backers, Careers Band |
/pricing/ | Pricing | Plans, Plan Comparison |
/contact/ | Contact | Contact, Contact Options, Customer Quotes |
/faq/ | FAQ | None |
/docs/ | Docs landing | Docs Hero, Docs Categories, Quickstart, Code Tabs, Docs Help |
/security/ | Security | Page Header, Compliance, Feature Grid, Questions, Disclosure |
/status/ | Status | Page Header, Status, Incidents, Newsletter |
/community/ | Community | Page Header, Community Channels, Open Source, Community Events, Contributors |
/testimonials/ | Testimonials | Page Header, Metrics, Customer Quotes, Quote Wall |
/login/, /signup/, /forgot-password/ | Log in and sign up | None. Each form holds the screen’s own fields, with no call to action |
/privacy-policy/, /terms-conditions/, /cookie-policy/, /components/, /elements/ | Other pages | None. Each holds the page and its text |
/blog/, /blog/{slug}/ | Blog | Listing: Blog List, Newsletter. Post: Newsletter, Related Posts |
/changelog/, /changelog/{slug}/ | Changelog | Listing: Changelog List. Entry: none |
/services/, /services/{slug}/ | Features | Listing: Page Header, Feature Index, Platform, Steps, Code Tabs, Feature Grid. Entry: Feature Hero, Feature Grid, Steps, Code Tabs, Customer Quotes, Related Features |
/solutions/, /solutions/{slug}/ | Solutions | Listing: Page Header, Feature Index, Customer Quotes, Questions. Entry: Feature Hero, Clients, Feature Grid, Code Tabs, Templates, Customer Quotes, Questions, Related Features |
/integrations/, /integrations/{slug}/ | Integrations | Listing: Page Header, Integrations Directory, Integrations Build. Entry: Related Integrations |
/customers/, /customers/{slug}/ | Customers | Listing: Page Header, Featured Story, Clients, Customer Stories, Customer Quotes. Entry: Metrics, Next Story |
/compare/, /compare/{slug}/ | Compare | Listing: Page Header, Compare List, Questions. Entry: Page Header, Plan Comparison, Feature Grid, Steps, Customer Quotes, Questions |
/careers/, /careers/{slug}/ | Careers | Listing: Page Header, Metrics, Feature Grid, Open Roles. Entry: Page Header |
/team/, /team/{slug}/ | Team | Listing: Page Header, Team Grid, Careers Band. Entry: Page Header |
| 404 | Section defaults, file not-found-section | None |
Blog category and tag pages, changelog tag pages, RSS feeds, llms.txt, and the Markdown copies are built from the entries above. Authors holds the people shown on blog posts.
New Entries
In Blog, Changelog, Features, Solutions, Integrations, Customers, Compare, Careers, Team, and Other pages, use Create New to add an entry. 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.
Sections
Section defaults holds the shared content of each section, in each language. A change there shows on every page that uses the section, unless the page has filled in its own block. To hide a section, turn off its Enable field: in Section defaults that hides it on every page, and in a page’s block on that page only.
| Where it appears | Sections |
|---|---|
| Homepages | Hero saas, Clients, Steps section, Stack section, Platform section, Metrics section, Customer quotes section, Code tabs section, Feature grid section, Regions section, Templates section, Security section, Plans section, Questions section, Changelog section |
/about/, /team/ | About hero section, Story section, Values section, Backers section, Careers band section, Team grid section |
/pricing/, /compare/ | Plans section, Plan comparison section, Compare list section |
/contact/ | Contact section, Contact options section |
/docs/ | Docs hero section, Docs categories section, Docs help section, Quickstart section |
/security/ | Compliance section, Disclosure section |
/status/ | Status section, Incidents section |
/community/ | Community channels section, Open source section, Community events section, Contributors section |
/testimonials/ | Quote wall section |
/blog/, /changelog/ | Blog list section, Related posts section, Newsletter section, Changelog list section |
/services/, /solutions/ | Feature index section, Feature hero section, Related features section |
/integrations/ | Integrations directory section, Integrations build section, Related integrations section |
/customers/ | Featured story section, Customer stories section, Next story section |
/careers/ | Open roles section, Benefits section |
/elements/ | Feature bento section |
| Every page | Call to action, Announcement bar, Cookie consent |
| 404 pages | Not found section |
Site-Wide Content
| Entry | What’s in it |
|---|---|
| Site settings | Site (title, description, tagline, Base Url, logo), Seo (including Robots Txt, Ai, and Sitemap), Settings, Opengraph, and Head for analytics tags |
| Menus | Header Primary (dropdowns and mega menus) and Footer, per language. See Menus |
| Social links | Your social profiles |
| Interface labels | Buttons, form messages, and other small text. Footer holds the footer description, copyright, and status text, and Ai holds the site summary, per language |
Under Settings, Layout picks the header (default, simple, or centered), the footer (default, minimal, or large), and the footer wordmark. A page can pick its own with the Header layout and Footer layout fields in its form. Settings also holds Sticky Header, Navigation Button, Navigation Secondary Link, Contact Form Action, Contact Form Provider, Contact Info, Subscription, Search, Smooth Scroll, Cookie Consent, Page Actions, Theme Credit, Animation, and Copyright.
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.
- Delete the empty line from the page’s file in
src/content/with a text editor.
What The Preview Doesn’t Update
Give a page about ten seconds to finish loading after it opens. If an edit doesn’t appear in the preview, check that the form you typed in is still the one open.
- The header, the menus, and values from Site settings don’t change while you type. They update when you save.
- Some Site settings also need
npm run devrestarted. The comment in the field says so. - The pricing toggle, tabs, and animated hero stop responding after a live update, until you reload the preview. Your published site is not affected.
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 and new page layouts. Then run
npm run tina:generateso the editor offers them. - Colors and type scale (
src/styles/theme.css) and fonts (src/config/fonts.json). - The list of languages. See Internationalization.
- Icon drawings (
src/layouts/helpers/Icons.astro). Icon names are editable as text. - A dropdown deeper than 4 levels: edit it in the menu file, then run
npm run tina:generateand the form follows it.
Versions And Testing
This edition is tested on Astro 7.3.8 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.
We have not run online editing against a live Tina Cloud project, and we have not run npm run setup:tina through to a connected project. Try one save on a copy of your site before you rely on it.
Do It With AI
I use the Tina edition. Tell me where to edit [TEXT OR SETTING] in /admin/: the entry, the languagefolder, the file, and the field. If it comes from Section defaults, say which pages will change,and how to change it on one page only. Don't change any files.