# What Is Editable In Tina ## What Is Editable In Tina **Files:** `src/content/`, `src/config/`, `src/i18n/` ยท **Skill level:** Beginner To open the editor, keep `npm run dev` running, open `http://localhost:4321/admin/`, and click **Enter Edit Mode**. You need no account on your own computer. See [Tina](../tina/) for the full guide. Everything below works in every language. Open the menu at the top left, pick an entry, a language folder, and a file. ### Where Each Page Is Edited "Own blocks" are section blocks in the page's form. Fill one in to change that section on this page only. | Address | Entry in `/admin/` | Own blocks | | ------- | ------------------ | ---------- | | `/` | **Home pages > Home 1** | Hero Section, Features Grid, About Section, Services Section, Cooperation Steps Section, Popular Skills Section, Stats Section, Projects Section, Testimonial Section, Faq Section, Blog Section, Brand Logos, Cta Gallery Section | | `/home-two/` | **Home pages > Home two** | Hero Section Two, Cta Video Section, Features Grid Two, About Section Two, Services Section Two, Stats Section, Projects Section Two, Mission Vision Section, Testimonial Section Two, Brand Logos Two, Team Section, Customized Technologies Section, Blog Section Two, Cta Gallery Section | | `/about/` | **About page** | Features Grid Two, About Section, Features Grid, Stats Section, Cta Video Section Two, Team Section, Brand Logos, Testimonial Section, Cta Gallery Section | | `/services/` | **Services**, the listing page | Services Section Two, Customized Technologies Section, Brand Logos, Cta Gallery Section | | `/services/{slug}/` | **Services**, one file per entry | Stats Section, Contact Section, Cta Gallery Section | | `/projects/` | **Projects**, the listing page | Projects Section, Contact Section, Cta Gallery Section | | `/projects/{slug}/` | **Projects**, one file per entry | Cta Gallery Section | | `/team/` | **Team**, with the members in its **List** | Team Section, Stats Section Two, Cta Section, Cta Gallery Section | | `/pricing/` | **Pricing** | Pricing Section, Customized Technologies Section, Cta Gallery Section | | `/faq/` | **FAQ** | Faq Section Two, Cta Section Two, Cta Gallery Section | | `/contact/` | **Contact page** | Contact Section Two, Cta Gallery Section | | `/blog/` | **Blog**, the listing page | Cta Gallery Section | | `/blog/{slug}/` | **Blog**, one file per entry | None | | `/privacy-policy/`, `/terms-conditions/`, `/components/` | **Other pages** | None | | The 404 page | **Interface labels**, under **Not Found** | None | Every row is repeated for each language at `/fr/` and `/ar/`. Category, tag, and page-number addresses under `/blog/` are made from your posts. On the `/services/` and `/projects/` listing pages, the block sets only the small heading above the list (and a button, on projects). The list itself is your entries. Blog authors are under **Authors**. ### Sections **Section defaults** holds the shared content of each section. Every page that shows the section uses it. | Section | Where it appears | | ------------------------------- | ---------------------------------------------------- | | About section | `/`, `/about/` | | About section two | `/home-two/` | | Blog section | `/` | | Blog section two | `/home-two/` | | Brand logos | `/`, `/about/`, `/services/` | | Brand logos two | `/home-two/` | | Contact section | Above the footer on `/`, `/projects/`, `/services/{slug}/` | | Contact section two | `/contact/`, including the form fields | | Cooperation steps section | `/` | | Cta gallery section | Nearly every page, above the footer | | Cta section | `/team/` | | Cta section two | `/faq/` | | Cta video section | `/home-two/` | | Cta video section two | `/about/` | | Customized technologies section | `/home-two/`, `/pricing/`, `/services/` | | Faq section | `/` | | Faq section two | `/faq/` | | Features grid | `/`, `/about/` | | Features grid two | `/home-two/`, `/about/` | | Hero section | `/` | | Hero section two | `/home-two/` | | Mission vision section | `/home-two/` | | Popular skills section | `/` | | Pricing section | `/pricing/`, including the plans | | Projects section | `/`, and the heading on `/projects/` | | Projects section two | `/home-two/` | | Services section | `/` | | Services section two | `/home-two/`, and the heading on `/services/` | | Stats section | `/`, `/home-two/`, `/about/`, `/services/{slug}/` | | Stats section two | `/team/` | | Team section | `/home-two/`, `/about/`, `/team/` | | Testimonial section | `/`, `/about/` | | Testimonial section two | `/home-two/` | The quotes are under **Testimonials**: **List**, and **List Home2** for Home two. The contact section above the first footer has no block on any page, so change it here. A few fields do nothing, because no section reads them: **Badge** on the Cta sections and the first Cta video section; **Description** on the Cta video sections and Customized technologies; **Image List**, **Video**, **Decorative Shape**, and **Sub Title** on Faq section two; **Enable** on the two Features grids; **Card Layout** on the two Projects sections; and **Decorative Image** on Testimonial section two. ### Site-Wide Content - **Site settings:** the site name, address, and logo, SEO, the AI files, forms, the footer description and background, smooth scroll, animation, the cursor, the theme credit, the Ask AI links, the Mailchimp form, your contact details, the header button, the announcement, and analytics tags. This is `config.toml`. - **Menus:** one file per language. **Header Primary** has the dropdowns and the mega menu. **Footer Primary** is the first footer, **Footer Secondary** the second, and **Footer Privacy** the copyright row in both. Menu items show in list order, so **Order** doesn't move them. In the footer, **Show** doesn't hide a link, so delete the row instead. - **Social links:** your social profiles. See [Social](../../customization/social/). - **Interface labels:** one file per language, with buttons, form messages, and footer copy (**Footer**). Techbyte has two headers and two footers. Every page's form has **Header layout** and **Footer layout**. Choosing **Choose an option** gives that page Header 1 and Footer 2. ### New Entries Open **Services**, **Projects**, **Blog**, or **Other pages**, then a language folder, then **Create New**, and pick the form. Type a **Title** and a file name at the bottom of the form: **Save** stays off until both are filled in. 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. An entry exists in one language. Add one with the same file name in every language folder, or the language switch on that page leads to a page that doesn't exist. If a new row in a list doesn't show, turn on its **Enable** or **Show** switch and fill in its image. A team member appears once it has a photo. Some sections also have a **Limit**: the team page shows 8 of its 10 sample members, so raise it in that page's **Team Section** block to show more. ### If You Clear A Field A field you never filled in a page's block 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. **Trailing Slash** and the **Multilingual** settings also need `npm run dev` restarted. Header and menu text, values from **Site settings** such as contact details, images with no description field, categories and tags, and short option values open only from their form, not by clicking them in the preview. ### What Stays In Code - Which sections a page has, and their order: the route in `src/pages/[...lang]/`. You can hide many sections with their **Enable** field. - Which version of a section a page shows, such as `HeroSection` or `HeroSectionTwo`: the route too. - 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`). - Favicons: `npm run generate-favicons`. - The list of languages. See [Internationalization](../../customization/internationalization/). ### Versions And Testing This edition needs Node.js 22 (22.22.0 or later) or 24. It is tested on Astro 7.2.8 and Node 22.23.4, 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, or a build with its keys. Try one save on a copy of your site before you rely on it. ### Do It With AI ```text I want to change [WHAT] on [PAGE ADDRESS] in the Techbyte Tina edition. Tell me which /admin/ entry and field holds it, and whether it is a section default that other pages share. If it needs a code change, make the change in every language, run npm run tina:generate if the forms changed, then run npm run tina:audit and npm run astro-check and tell me the results. ```