What Is Editable In Tina

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. The one-page sites under /landing/ use the same files as their homepages.

Authors holds the post authors, and Testimonials holds the quotes in the sliders.

New Entries

Use Create New to add a post, a solution, or another 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.

The other files in Section defaults aren’t on any demo page, so they open with no preview: About video stats, Blog grid, Contact split, Cta circle, Join team section, Portfolio slider, Portfolio slider panel, Process section, Roadmap section, Services slider, Solution steps counter, Solution steps slider, Teamwork section, Testimonial slider video, and Work with us section.

To hide a section, turn off its Enable field: in Section defaults on every page, and in a page’s block on that page only.

Site-Wide Content

Settings holds the header and footer options: Sticky Header, Header Top Bar with its Layouts (the top bar style of each header), Office Dropdown, Header Offcanvas (the contact drawer), Header Actions, Navigation Button, Contact Info (phone and email), Footer Description, Company Desk, Copyright, Subscription, and Theme Credit. It also has Contact Form Action, Contact Form Provider, Smooth Scroll, Keyboard Scroll, Cursor, and Page Actions. Which header and footer a page uses stays in code.

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. A switch you never touched shows as off, even when the section is visible, because the page uses the default.

Tina can’t bring the default back by itself. To get the text back, copy it from Section defaults into the field, or delete that line from the page’s file in src/content/ with a text editor.

What The Preview Doesn’t Update

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 dev restarted: language settings, folder names, Base Url, and Trailing Slash.

Click-to-edit doesn’t reach images with no alt field, categories and tags, stat suffixes, options groups, case study metadata, or social link labels. Change them in their forms. The Components page and the sample post gap-between-strategy-execution use raw HTML, so their bodies are edited as source code.

What Stays In Code

• Which sections a page has, and their order: the route in src/pages/[...lang]/.
• Which header and footer a page uses: settings on the page’s route.
• New sections, new page routes, and new layouts of a section. Then run npm run tina:generate so the editor offers them.
• Colors and type scale (src/styles/theme.css) and fonts (src/config/fonts.json).
• The list of languages. See Internationalization.
• Redirects from old addresses (astro.config.mjs).
• The icons themselves. Icon names are text you can edit.

Versions And Testing

This edition is tested on Astro 7.4.2 and Node 22, with tinacms 3.15.1, @tinacms/cli 4.0.4, and @tinacms/astro 0.8.0. npm ci installs exactly these. 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, so npm run setup:tina and the online build are untested. 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 language
folder, 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.