# Site Identity & Logo

## Site Identity & Logo

**Files:** `src/config/config.toml`, `src/i18n/<language>.json`, `src/lib/brandMark.ts`, `src/assets/images/` · **Skill level:** Beginner

Your site's name, the line after every page title, the wordmark in the header and footer, the small icon in the browser tab, and the card people see when they share a link. Your registration number, phone, address, and office hours are separate: see [Organization Info](/givo/customization/organization-info/).

### Name, Tagline, And Address
```toml
# src/config/config.toml
[site]
  title            = "Givo"
  description      = ""
  tagline          = ""
  taglineSeparator = ""   # default is " - "
  baseUrl          = "https://example.com"   # PLACEHOLDER: set your own domain before deploying
```

- `title` is your organization's name. It is the browser title of the home page (the main homepage's `title` is empty, so it uses this), the `{brand}` in the footer copyright, the name on the social cards, and the organization name in structured data while `[organization] name` is empty.
- `description` is the default text under your link in search results and social previews. Pages with their own `description` or `metaDescription` use theirs. Empty uses `seo.siteDescription` in each `src/i18n/<language>.json`. A value here is used for every language.
- `tagline` is added to every page title: "Events - your tagline". Empty uses `seo.tagline` in each `src/i18n/<language>.json`. A value here is used for every language. Set `disableTagline: true` in a page's frontmatter to drop it on that page.
- `baseUrl` must be your real address before you launch. Canonical links, the sitemap, `robots.txt`, RSS feeds, `llms.txt`, and social previews are built from it. While it is still `https://example.com`, `npm run build` prints a warning. A `SITE_URL` environment variable on the build overrides it (`vercel.sh` sets one on Vercel).

### The Tagline In Each Language
Givo ships with the tagline and description empty in `config.toml`, so each language uses its own. They are under `seo` in the language files:

```json
// src/i18n/en.json
"seo": {
  "tagline": "Charity & Non-Profit Astro & Tailwind CSS Theme",
  "siteDescription": "An Astro and Tailwind CSS theme for charities and non-profits: ..."
}
```

The shipped text describes the theme, not your organization, so change it in `en.json`, `fr.json`, and `ar.json`. Write a short line about your work, for example "Clean water and school meals in the north". Set `tagline` to `""` in a language file to end that language's page titles with the organization name instead.

### The Wordmark
Givo's logo is a wordmark: your name in the heading font, with a small green heart as the dot of its first "i".

```toml
[site]
  logo       = ""        # Leave empty for the wordmark
  logoText   = "Givo"    # Shown exactly as typed. Its first "i" gets the heart as its dot
  logoWidth  = "28px"    # Only when `logo` is set
  logoHeight = "28px"    # Only when `logo` is set
```

**Change only the name.** Set `logoText` to your name, written the way you want it shown: `"Riverside Food Bank"` stays as typed. If the name has an "i", the heart replaces the dot of the first one. If it has none, the heart sits before the text. Check the header at phone width afterwards: a long name has less room next to the menu button.

**Change the heart.** `src/lib/brandMark.ts` holds the heart as an SVG path on a 32×32 grid (`heart`), and the rounded tile drawn behind it in the favicon, the announcement bar, and the generated social cards (`tile`). The wordmark letters use the text color, so they follow light and dark mode. The heart uses the green accent. Edit this file only if you are comfortable with SVG paths.

**Use your own logo file.** Put the file (SVG is best, PNG works) in `src/assets/images/` or `public/`, and point `logo` at it:

```toml
[site]
  logo       = "/images/my-logo.svg"   # src/assets/images/my-logo.svg
  logoWidth  = "120px"
  logoHeight = "28px"
```

Set `logoWidth` and `logoHeight` to keep your logo's proportions at about 28 px tall. An image in `logo` replaces the wordmark.

<Aside type="caution" title="One logo file for every background">
  An image in `logo` is used as it is everywhere: on the light header, in dark
  mode, and on the forest-green `default` footer. Pick a logo that reads on
  light and dark backgrounds, or keep the wordmark, which changes color on its
  own.
</Aside>

`src/assets/images/logo.svg` and `logo-on-dark.svg` are the Givo wordmark as an image, for light and dark backgrounds: "Givo" in Urbanist Bold with the heart over the "i", drawn as outlines so they look the same without the font. The site doesn't use them; they are there for your email signature or documents. Replace or delete them.

### Favicons
The small icon in the browser tab and on phone home screens. Givo creates every size from one image:

1. Save a square image of your mark in `src/assets/images/`: an SVG, or a PNG of at least 512×512 px. The shipped one is `src/assets/images/favicon.svg`, the heart on a forest tile.
2. Point `[site.favicon] image` at it. The path starts with `/images/` and is read from `src/assets/`:

   ```toml
   [site.favicon]
     path  = "/images/favicons"     # favicon images path (No need to change it)
     image = "/images/favicon.svg"  # src/assets/images/favicon.svg
   ```

3. With `npm run dev` running (it applies your `config.toml` change), run:

   ```bash
   npm run generate-favicons
   ```

The files are written to `public/images/favicons/`. Hard-refresh the browser (<kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>R</kbd>, or <kbd>Cmd</kbd> + <kbd>Shift</kbd> + <kbd>R</kbd> on a Mac) to see the new icon; browsers keep old favicons for a long time.

### Social Preview Images
When someone shares a link to your site, the preview card is, in this order:

1. **The page's own `image`**, if its frontmatter has one, cropped to 1200×630. Causes, events, and stories have one.
2. **A generated card.** With `[opengraph] generateImages = true` (the default), `npm run build` draws a 1200×630 card for every page without an `image`: your wordmark, the section name, the page title, and its description, in your fonts and colors.
3. **The shared image** in `[opengraph] image`, when cards are off.

```toml
[opengraph]
  image          = "/images/og-image.jpg"   # public/images/og-image.jpg
  generateImages = true                     # a card for every page without an `image`
  theme          = "light"                  # light | dark: palette for the cards and npm run generate-og-image
```

The generated cards are made during the build only, so you won't see them with `npm run dev`. After a build they are in `dist/og/`.

The shipped `public/images/og-image.jpg` shows the Givo name. Make your own once your name, tagline, colors, and `baseUrl` are set:

```bash
npm run generate-og-image
```

It redraws `public/images/og-image.jpg` with your wordmark, tagline, and description, in the same style as the page cards. It reads `[site] baseUrl` from `config.toml` (not `SITE_URL`). You can also replace the file with your own 1200×630 image.

More in [SEO & AI Visibility](/givo/customization/seo-ai-visibility/).

### Before You Launch
- [ ] `title` and `logoText` are your organization's name.
- [ ] `seo.tagline` and `seo.siteDescription` describe your work in every language file, or you set `tagline` and `description` in `[site]`.
- [ ] `baseUrl` is your domain.
- [ ] The favicon is your mark, and you ran `npm run generate-favicons`.
- [ ] You ran `npm run generate-og-image`, or replaced `public/images/og-image.jpg`.
- [ ] The header logo looks right at 375 px wide, in light and dark mode, and at `/ar/`.

### Do It With AI
```text
Rebrand the site to "[NAME]". In [site] of src/config/config.toml set title and logoText to
"[NAME]" and baseUrl to "[URL]". In every src/i18n/<language>.json, set seo.tagline to a short
line about our work ([WHAT WE DO, WHERE]) and seo.siteDescription to one sentence about it,
translated for each language. [I put my logo at src/assets/images/[FILE].svg: set logo to
"/images/[FILE].svg" and logoWidth / logoHeight for a 28px-tall logo.] Then tell me which npm
commands to run.
```