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. The file called -index is the page itself, or the listing page in a group of entries. 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. A section with no block here uses its content from Section defaults.

The header and footer are on every page, so they have no blocks. See Site-Wide Content below.

Testimonials holds the client quotes the testimonial sections show. Authors isn’t shown on the site: a blog post shows the name typed in its own Author field. Media Manager holds all the images in src/assets/images/.

New Entries

Open the language folder first, so the new file lands in it. Click Create New, and choose the form for a new entry, not “Listing page”. Fill in the title and, at the bottom of the form, the filename, which becomes the page’s address. A new entry exists only in that language, so repeat it in each language folder.

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. Set the date on a blog post too: the form shows today’s date, but saves it only if you change it, and a post with no date comes first in the blog list.

Sections

Section defaults holds the shared content of each section, in each language, including the pricing plans (pricing-section), the FAQ questions (faq-section), and the awards (award-section). A change there shows on every page that uses the section, unless the page has filled in its own block.

To hide a section on every page, turn off its Enable field in Section defaults. Call to action widget has no such field.

Site-Wide Content

Settings holds the header and footer options: Sticky Header, Navigation Button, Header Offcanvas (Enable and Logo), Footer Description, Company Desk, Copyright, Contact Info, and Theme Credit. It also has Contact Form Action, Contact Form Provider, Smooth Scroll, Page Jump, Cursor, and Page Actions. Veltro has one header layout and one footer layout, so there are no layout options to pick. A page file sets the header’s position and border in code.

If You Clear A Field

In a block, a field you never filled uses the default. A field you clear is saved empty, and that text disappears from this page, on the finished site too.

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 that line from the page’s file in src/content/ with a text editor.

A list you empty in a block shows nothing on this page. An image you remove from a block goes back to the section default’s image, because Tina leaves the empty value out of the file.

The Enable switch in a block looks off until you set it, even though the section is showing, and it changes nothing while you leave it alone. To hide a section on one page, turn Enable on, then off, and save.

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. Restart npm run dev after you change Trailing Slash or anything under Multilingual.

Other things that only happen in the editor:

• Reveal animations are off, so all content stays visible.
• A click on outlined text opens its field. To try a button, the pricing switch, or a form, open the normal page at http://localhost:4321/.
• Images with no alt text, categories and tags, and one-word options have no outline. Change them in their forms.
• The Components page uses raw HTML, so its body is edited as source code.

What Stays In Code

• Which sections a page has, and their order: the page file in src/pages/[...lang]/.
• New sections and new page layouts. 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.
• The icons themselves. Icon names are text you can edit, and AGENTS.md says how to add one to the list.
• The folder names. Leave the Folder values in Site settings alone unless you also rename those folders and change the code.
• A few fields in the forms do nothing, because no part of this theme reads them: Subscription in Site settings and Interface labels (there is no newsletter form), and Description and Button under Header Offcanvas in Site settings (the side panel’s text is in Interface labels).

Versions And Testing

This edition is tested on Astro 7.3.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. 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.