What Is Editable In Tina
Files: tina/, src/content/, src/config/, src/i18n/ · Skill level: Beginner
Run npm run dev and open http://localhost:4321/admin/. No account is needed. Tina explains how to open the editor and how to edit online. Everything you edit is saved to the files in the project, in every language.
Where Each Page Is Edited
Open the menu at the top left, then pick the entry, a language folder, and a file. Blocks means the page’s form has its own blocks, so you can change a section for that page only.
| Address | Entry in /admin/ | Blocks |
|---|---|---|
/, /home-2/, /home-3/ | Home pages: -index, home-2, home-3 | Yes |
/features/ | Features page | Yes |
/pricing/ | Pricing page | Yes |
/about/ | About page | Yes |
/testimonials/ | Reviews page | Yes |
/contact/ | Contact page | Yes |
/request-demo/ | Request a demo page | Yes |
/faq/ | FAQ page | Yes |
/help/ | Help center | Yes |
/status/ | Status page | Yes |
/integrations/ | Integrations: -index | Yes |
/integrations/ + entry | Integrations: one file per entry | No |
/solutions/ | Solutions: -index | Yes |
/solutions/ + entry | Solutions: one file per entry | Yes |
/templates/ | Templates: -index | Yes |
/templates/ + entry | Templates: one file per entry | No |
/careers/ | Careers: -index | Yes |
/careers/ + entry | Careers: one file per entry | No |
/blog/ | Blog: -index | Yes |
/blog/ + post | Blog: one file per post | Related articles only |
/changelog/ | Changelog: -index | Yes |
/changelog/ + release | Changelog: one file per release | No |
| Category, tag, and page lists | Built from Blog and Changelog entries | No |
/privacy-policy/, /terms-conditions/, /cookie-policy/, new text pages | Legal and text pages | No |
/login/, /signup/, /forgot-password/ | Log in and sign up | No |
/elements/ | Shared pieces: the layout gallery labels | No |
| 404 | Section defaults: the not found section | No |
The people in the author box on posts are under Authors.
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. Every page that shows a section uses it.
| Section | Where it appears |
|---|---|
| Hero, Integrations | /, /home-2/, /home-3/ |
| Logos | /, /home-2/, /about/, /pricing/, and inside the sign-up hero on /home-3/ |
| Why | /, /home-2/ |
| Features | /, /features/ |
| Overview | /, /about/ |
| Testimonials | /, /home-3/, /about/, /testimonials/, /solutions/, solution pages |
| Pricing | /, /home-2/, /pricing/ |
| FAQ | The three homepages, /features/, /pricing/, /faq/, solution pages |
| Stats panel, Solution tabs, Latest posts | /home-2/ |
| Proof | /home-2/, /pricing/ |
| Feature rows | /home-2/, /home-3/, solution pages |
| Intro, Bento, Control panel | /home-3/ |
| Steps | /home-3/, solution pages |
| Comparison | /home-3/, /solutions/, solution pages |
| Feature collage, Feature summary, Numbers | /features/ |
| Benefits | /features/, /careers/ |
| Plan compare | /pricing/ |
| Mission, Stats, Team | /about/ |
| Company values | /about/, /careers/ |
| Contact cards, Contact message | /contact/ |
| Demo form, Demo reasons | /request-demo/ |
| Integrations catalog, Integration detail | /integrations/, each integration page |
| Templates catalog, Template detail | /templates/, each template page |
| Solutions list | /solutions/ |
| Careers list, Career detail | /careers/, each job page |
| Blog posts, Related articles | /blog/, under each post |
| Release notes | /changelog/ |
| Help categories, Popular articles | /help/ |
| Status | /status/ |
| Call to action | Every page except the log-in, sign-up, and password screens |
| Not found | The 404 page |
Site-Wide Content
- Site settings: name, address, logo, SEO, forms, search, cookie banner, smooth scroll, animation, page action links, copyright, theme credit, contact details, newsletter, the header button and text link, Open Graph, and the tags in Head.
- Menus: Header Primary (dropdowns and mega menus) and Footer, per language.
- Social links: your social profiles.
- Interface labels: buttons, form messages, and footer copy, per language.
- Shared pieces: the dashboard’s sample data, the cookie banner, the announcement bar, and the
/elements/labels, per language.
Taskly has three header layouts and four footer layouts. Each page form picks them with Header layout (default, bar, islands) and Footer layout (default, wordmark, newsletter, tiles).
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 restore it, copy the text back from Section defaults, or remove the empty line from the file.
What The Preview Doesn’t Update
The header and menus, and values from Site settings, don’t update while you type. They update when you save. Some Site settings also need npm run dev restarted: the comment in the field says so. Online there are forms only, because the live preview and click-to-edit need npm run dev on your computer.
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.
- The icon set, and the layout of the coded product mockups. Icon names and the mockups’ data are editable.
- The structure of the forms in
src/layouts/components/forms/. Their fields and labels are editable.
When Tina saves a file, 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 description under each field.
Versions And Testing
This edition is tested on Astro 7.3.8 and Node 22 (Tina’s command-line tool supports Node 22 and 24 only), 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. Try one save on a copy of your site before you rely on it.
Do It With AI
I use the Tina edition of Taskly. I want to change [WHAT] on [PAGE]. Tell me which entry to open at/admin/, which language folder and file to pick, and which field to change. Tell me if the text comesfrom Section defaults, so I know the change reaches every page that uses that section. If it can'tbe done in the editor, say which file to change. Don't change any files yet.