# Quick Start

## Make Givo Yours In 30 Minutes

**Skill level:** Beginner · **Time:** 30 minutes · **You need:** the site running with `npm run dev` ([Installation](/givo/getting-started/installation/))

This page walks through the ten changes almost every site needs, in order. Each step names one file and the exact lines to edit, and links to the page with the details. Save the file and the browser shows the change, `config.toml` included.

This page shows the files. In the Tina edition you can make the same changes at `/admin/`, and in the Sanity edition most of them are in the Studio. See [What Is Editable In Tina](/givo/features/what-is-editable-tina/) and [What Is Editable In Sanity](/givo/features/what-is-editable-sanity/).

<Aside type="tip">
  Before you start, save a copy of the untouched theme (or commit it with git) so
  you can always compare or go back. See [Editing Safely](/givo/beginner/editing-safely/).
</Aside>

<Steps>

1. **Name your site and set its address**

   Open `src/config/config.toml` and edit the `[site]` block:

   ```toml
   [site]
     title    = "Riverside Food Bank"
     baseUrl  = "https://www.your-domain.org"
     logoText = "Riverside Food Bank"
   ```

   - `title` is your organization's name. The footer copyright and the structured data use it. The homepage's browser title comes from `metaTitle` in `src/content/homepage/english/-index.md`; change it there.
   - `logoText` is the wordmark in the header. Its first "i" gets the heart as its dot; a name without an "i" gets the heart before the text.
   - `baseUrl` is your live address. The theme ships with the placeholder `https://example.com`, and `npm run build` prints a `[site]` warning until you change it. Canonical links, the sitemap, `robots.txt`, RSS feeds, `llms.txt`, and social previews all use it.
   - Every page title ends with a tagline (`<page> - <tagline>`). Each language has its own, in `seo.tagline` in `src/i18n/<language>.json`, next to `seo.siteDescription` (the description of pages without their own). Rewrite both in every language. A `tagline` or `description` set in `[site]` is used for every language instead.

   Details: [Site Identity & Logo](/givo/customization/site-identity-logo/) and [Config Reference](/givo/customization/config-reference/).

2. **Add your organization details**

   Your organization's details live in one place, `[organization]` in the same file. The header, footer, contact page, donation form fine print, event pages, structured data, and `llms.txt` all use them:

   ```toml
   [organization]
     name               = ""            # empty uses site.title
     legalName          = ""            # registered legal name, if different
     registrationNumber = "12-3456789"  # your charity or non-profit number; empty hides it
     email              = "hello@your-domain.org"

     [organization.address]
       show       = true                # false = no public street address
       street     = "100 Example Street, Suite 200"
       locality   = "Springfield"
       region     = "ST"
       postalCode = "00000"
       country    = "US"
   ```

   Every value marked `# sample` in the file is a placeholder: the shipped registration number, email (`hello@example.org`), and address are not real. Details: [Organization Info](/givo/customization/organization-info/).

3. **Set your phone number and office hours**

   Still in `[organization]`:

   ```toml
   [organization]
     phone        = "+15550100199"     # digits with country code, for tap-to-call links
     phoneDisplay = "(555) 010-0199"   # how the number is shown
     timezone     = "America/New_York" # office hours and event times
     closedDates  = ["2026-12-25", "2027-01-01"]

     [organization.hours]
       mon = "09:00-17:00"
       fri = "09:00-16:00"
       sat = ""                        # empty = closed
   ```

   The shipped number is in the fictional `555-01xx` range: replace it. Leave `phone` empty to hide every call link. Hours use the 24-hour clock, and `"08:00-12:00,13:00-17:00"` gives a lunch break. A wrong value prints an `[organization]` warning in the terminal and is ignored, so watch the terminal after you save.

4. **Set your currency and donation amounts**

   Donation numbers are not typed into pages. They come from one file, `src/content/donate/english/-index.md`, which feeds the donation form, the quick donate panel on the homepage, the monthly giving tiers, and the impact lines under each amount:

   ```yaml
   currency: "USD" # ISO 4217 code, one currency for every language
   amounts:
     oneTime: [25, 50, 100, 250, 500] # preset buttons, one-time
     monthly: [10, 20, 35, 50, 100] # preset buttons, monthly
   default:
     oneTime: 50
     monthly: 20
   minimum: 5 # smallest custom amount
   coverFeesPercent: 3 # 0 hides the "cover the fees" line
   impactMap:
     - amount: 25
       label: "school supplies for one child"
   ```

   The amounts and the outcomes in `impactMap` and `tiers` are samples: replace them with your own costs. Copy the same numbers into the file of every other language, such as `src/content/donate/french/-index.md`: `npm run build` prints a `[donate]` warning when they differ. Details: [Donation Form](/givo/customization/donation-form/) and [Giving Tiers & Receipt](/givo/customization/giving-tiers-receipt/).

5. **Connect the donation form to your payment provider**

   Until you do, the form sends nothing, and the dev server shows a notice inside it. In the same file, pick one of two ways:

   ```yaml
   form:
     mode: "form" # form | redirect
     endpoint: "" # "form": the URL your payment provider or form service gives you
     method: "post"
     processorUrl: "" # "redirect": a hosted checkout, e.g. "https://checkout.example.org/donate?amount={amount}&interval={frequency}"
     thanksUrl: "/donate/thanks/"
   ```

   - `mode: "form"` sends every field to `endpoint`.
   - `mode: "redirect"` sends the donor to `processorUrl`, a hosted checkout page from your provider or donation platform. `{amount}`, `{frequency}`, and `{cause}` in it are filled in.

   Set the same `form` values in every language. Details: [Donation Form](/givo/customization/donation-form/).

6. **Replace the sample causes**

   The 9 causes in `src/content/causes/english/` are samples. Each file is one cause, and its file name is its URL (`clean-water-wells.md` is `/causes/clean-water-wells/`):

   ```yaml
   title: "Clean water wells"
   category: "water" # id from `categories:` in -index.md
   goal: 75000 # sample
   raised: 48900 # sample
   donors: 640 # sample
   deadline: 2027-04-30 # sample; remove for an ongoing cause
   featured: true
   ```

   Rename or copy a file for each real cause and set your own goal, amount raised, and donors. These are numbers you update by hand: the site does not count gifts. The progress bar and the days left come from them, and the days left are counted when the site is built, so rebuild the site every day while an appeal runs. Add each cause to the Causes mega menu in each `src/config/menu.<language>.json`. Details: [Causes & Campaigns](/givo/customization/causes-campaigns/).

7. **Set your brand colors and logo**

   Open `src/styles/theme.css`. The light colors are in the `:root` block, and the dark-mode colors in the `:root.dark` block below it:

   ```css
   :root {
     --theme-primary: #087f44; /* green: buttons, links, progress bars */
     --theme-accent: #087f44;
     --theme-gold: #e6b35a;    /* the donation panel and small marks */
     --theme-band: #0f2a1f;    /* forest: the footer and solid bands */
   }
   ```

   Change the matching lines in `:root.dark` too, then check both modes with the light/dark button in the header.

   Givo draws a built-in wordmark with a heart from `logoText`. To use your own logo file instead, put it in `public/` or `src/assets/` and set `logo` in `[site]` (with `logoWidth` and `logoHeight`). Then set `[site.favicon] image` to a square version of your logo and run `npm run generate-favicons`. Details: [Colors & Fonts](/givo/customization/colors-fonts/) and [Site Identity & Logo](/givo/customization/site-identity-logo/).

8. **Connect the contact, volunteer, and newsletter forms**

   The contact, volunteer, and fundraise forms post to a placeholder address until you change it in `config.toml`. The dev server shows a warning inside each form, and `npm run dev` and `npm run build` print a `[forms]` line, until you do:

   ```toml
   [settings]
     contactFormAction   = "https://formsubmit.co/you@your-domain.org"
     contactFormProvider = "formsubmit.co"   # formsubmit.co | formspree | netlify
   ```

   The newsletter sign-up needs your Mailchimp address in `formAction` under `[settings.subscription]`. Details: [Forms](/givo/customization/forms/).

9. **Replace the photos**

   The sample photos are in `src/assets/images/photos/`, named by use (`cause-`, `event-`, `story-`, `team-`, `gallery-`, and so on). Content files point at them with paths that start with `/images/`:

   ```yaml
   image: "/images/photos/cause-water-tap.jpg"
   imageAlt: "Your own description of the photo"
   ```

   Put your own photo in the same folder and change the path and the alt text, in every language folder. `IMAGE-CREDITS.md` lists every sample photo, so you can tick them off. Details: [Icons & Images](/givo/customization/icons-images/).

10. **Check, build, and deploy**

    Stop the dev server and run:

    ```bash
    npm run astro-check
    npm run build
    ```

    Fix anything `astro-check` reports. Read the yellow lines in the build output: `[site]` means `baseUrl` is still the placeholder (step 1), `[forms]` means a form still posts to a placeholder or the donation form is not connected (steps 5 and 8), and `[donate]` means the donation files of your languages differ (step 4). Then follow the [Deployment](/givo/deployment/) guide, which has the full launch checklist.

</Steps>

### What Next?
- Pick your homepage: Givo has three (`/`, `/home-appeal/`, `/home-community/`). See [Homepages](/givo/customization/homepages/).
- Only need English? See [Internationalization](/givo/customization/internationalization/).
- Point the header button and menus at your pages, and hide the **Pages** demo menu: [Header](/givo/customization/header/) and [Menus](/givo/customization/menus/).
- Replace the sample events: [Events & Calendar](/givo/customization/events-calendar/).
- Replace the sample figures on `/impact/` and the "where your money goes" split: [Impact & Transparency](/givo/customization/impact-transparency/).
- Replace the demo content page by page: [Pages](/givo/customization/pages/) lists every page and its file.
- Try the other layouts of your sections: [Section Layouts](/givo/customization/section-layouts/).
- Let an AI assistant do the repetitive work: [Prompt Library](/givo/ai-customization/prompt-library/).