# 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**. Open the menu at the top left, then pick an entry, a language folder, and a file. The full guide is at [Tina](../tina/).

### Where Each Page Is Edited
"Its own blocks" are the fields in the page's form that change a section on that page only. Every other section on the page comes from **Section defaults**.

| Address | Entry in `/admin/` | Its own blocks |
| ------- | ------------------ | -------------- |
| `/` | Home page | Home Banner, Customers, About Us, Services, How It Works, Portfolio, Testimonial, Blog, and Call To Action sections |
| `/about/` | About page | About Banner, Achievements, Our Team, and Call To Action sections |
| `/contact/` | Contact page | Contact, Office Locations, and Call To Action sections |
| `/faq/` | FAQ | Call To Action section. The questions are in this form |
| `/pricing/` | Pricing | Pricing, Testimonial, Faq, and Call To Action sections |
| `/team/` | Team page | Our Team, Leadership Team, Join Us section, and Call To Action section. The team members are in this form |
| `/services/` | Services, listing page | Index Services section and Call To Action section. Its Services and Faq sections show on every service page |
| `/services/{slug}/` | Services, one file per service | Services section, on top of the listing page's. Intro, Details, and Impact are in this form |
| `/case-studies/` | Case studies, listing page | Index Portfolio section and Call To Action section |
| `/case-studies/classic/`, `/case-studies/classic-masonry/`, `/case-studies/overlay/` | Case studies, listing page | Index Portfolio section. The layout stays in code |
| `/case-studies/{slug}/` | Case studies, one file per case study | No |
| `/career/` | Careers, listing page | Our Values, Career Openings, and Call To Action sections. Intro, Apply Block, Benefits, and Social are in this form |
| `/career/{slug}/` | Careers, one file per job | No |
| `/blog/` | Blog, listing page | Call To Action section. Settings and Single are in this form |
| `/blog/modern/` | Blog, listing page | No |
| `/blog/{slug}/` | Blog, one file per post | No |
| `/blog/single-minimal/` | Blog, the first post | No |
| `/blog/category/...`, `/blog/page/...` | Blog, listing page, and each post's **Categories** | No. These are built from your posts |
| `/privacy-policy/`, `/terms-conditions/` | Other pages | No |
| `/elements/` | Other pages. Its body is edited as source code | No |
| 404 | Interface labels, **Not Found** | No |
| `/llms.txt`, `/llms-full.txt`, `.md` copies, `/robots.txt`, sitemap | No form of their own. They are built from your content, with switches in **Site settings > Seo** | No |

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
These are the forms under **Section defaults**, one set per language. A change here shows on every page that uses the section, unless that page has its own value.

| Section | Where it appears |
| ------- | ---------------- |
| Home banner, Customers, About us, How it works, Blog section | The homepage |
| Services section | The homepage, `/services/`, and each service page |
| Portfolio section | The homepage and the case study lists |
| Testimonial section | The homepage and `/pricing/` |
| About banner, Achievements | `/about/` |
| Our team | `/about/` and `/team/` |
| Join us | `/team/` |
| Pricing section | `/pricing/` |
| Contact section, Office locations | `/contact/` |
| Our values, Career openings | `/career/` |
| Call to action | Near the bottom of most pages, including posts, case studies, jobs, and services |

**Sidebar call to action** has its own entry in the menu. It is the box in the sidebar of the blog list and case study pages.

The FAQ list has no section default: it is in the **FAQ** form. Service pages read their Intro, Details, and Impact from each service's form.

### Site-Wide Content
- **Site settings:** **Site** (title, address, logo, favicon), **Seo** (author, keywords, robots, sitemap, AI files), **Settings** (sticky header, brand name, forms, footer signup, copyright, theme credit, languages, contact details, Ask AI links, smooth scroll, header button), **Opengraph**, and **Head** for analytics tags.
- **Menus:** **Header Primary**, with dropdowns and mega menus, and **Footer Menu Quick Link**, **Footer Menu Resources**, **Footer Menu Legal**, and **Footer Menu**, one file per language. See [Menus](../../customization/menus/).
- **Social links:** your social profiles.
- **Interface labels:** buttons, form messages, footer copy, the 404 page, and the site's tagline and description, one file per language.

Looka has one header and one footer, so there is no layout option for them.

In **Site settings**, leave **Tagline**, **Description**, **Footer Description**, and **Copyright > Text** empty, because a value there replaces the **Interface labels** text in every language. Leave **Blog Folder**, **Services Folder**, and **Portfolio Folder** as they are, because changing one also needs folders and routes renamed in code.

### If You Clear A Field
A field you never filled uses the section default. A field you clear is saved empty, and that hides the 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. Use the **Enable** field to hide a whole section.

Clicking text in the preview opens the file the text comes from. If that is a section default, your edit changes every page that uses it.

### What The Preview Doesn't Update
- The header and menus, and values from **Site settings**, don't update as you type. They update when you save.
- **Trailing Slash** and the **Multilingual** group in **Site settings** also need `npm run dev` restarted.
- After a live update, the contact form, sticky sidebars, table of contents highlight, magnetic buttons, line animation, and accordion group closing can stop responding in the preview until you reload it. Your saved pages are not affected.
- Fade-in animations are off in the preview.
- Click-to-edit doesn't reach the header and menus, values from **Site settings** such as contact details, images with no alt field, categories and tags, and option values. Edit those in the form.

### 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:generate` so the editor offers them.
- Colors and type scale (`src/styles/theme.css`) and fonts (`src/config/fonts.json`).
- The white footer logo: replace `src/assets/images/logo-white.svg`.
- The list of languages: `src/config/language.json`. See [Internationalization](../../customization/internationalization/).
- The structure of the contact form. Its fields and labels are in **Section defaults > Contact section**.
- Line art and icons in components. Icon names are editable as text.

### Versions And Testing
This edition is tested on Astro 7.2.6 and Node 22, with `tinacms` 3.15.1, `@tinacms/cli` 4.0.4, and `@tinacms/astro` 0.8.0. The Tina packages 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
```text
I use the Tina edition of Looka. Tell me where to edit [WHAT I WANT TO CHANGE] in /admin/: the
entry, the file, and the field. If it is a section, say whether to change it in Section defaults
(every page that uses it) or in the page's own form (that page only). If it stays in code, make
the change in every language, then run npm run astro-check and npm run tina:audit and tell me the
results.
```