# Quick Start

## Make Plumbo Yours In 30 Minutes

**Skill level:** Beginner · **Time:** 30 minutes · **You need:** the site running with `npm run dev` ([Installation](/plumbo/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](../../features/what-is-editable-tina/) and [What Is Editable In Sanity](../../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](/plumbo/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       = "Acme Plumbing"
     description = "Licensed plumbers for leaks, drains, and water heaters, priced up front."
     tagline     = "Plumbing and drains in Your Town"
     baseUrl     = "https://www.your-domain.com"
     logoText    = "Acme Plumbing"
   ```

   - `title` is your brand 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.
   - `tagline` is added to every page title (`<page> - <tagline>`), so make it a short line about your business. A `tagline` or `description` set here is used for every language. Leave them empty to use each language's own, in `src/i18n/<lang>.json`.
   - `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.

   Details: [Config Reference](/plumbo/customization/config-reference/).

2. **Add your business details**

   Your company details live in one place, `[business]` in the same file. The header, footer, contact page, area pages, booking form, and the structured data search engines read all use them:

   ```toml
   [business]
     name  = ""                    # empty uses site.title
     type  = "Plumber"             # schema.org type; the comment in the file lists the others
     email = "hello@your-domain.com"

     [business.address]
       show       = true           # false = you visit customers and have no public address
       street     = "12 Example Road"
       locality   = "Your Town"
       region     = "ST"
       postalCode = "00000"
       country    = "US"
   ```

   Every value marked `# sample` in the file is a placeholder: the shipped email is `hello@example.com`. Details: [Business Info](/plumbo/customization/business-info/).

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

   Still in `[business]`:

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

     [business.hours]
       mon = "07:30-18:00"
       sat = "08:00-14:00"
       sun = ""                        # empty = closed
   ```

   The shipped number is a fictional `555` number: 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 a `[business]` warning in the terminal and is ignored, so watch the terminal after you save.

4. **Set your services and prices**

   Prices are not typed into pages. They come from one file, `src/content/pricing/english/-index.md`, which feeds the estimator, the booking form, the rate sheet, the add-ons, and the "from" prices on service cards. Each service has one rate card, priced by the hour or per unit:

   ```yaml
   rateCards:
     - id: "pipe-repair"
       label: "Pipe repair"
       mode: "hourly" # hourly | units
       hourlyRate: 115 # sample
       callOutFee: 89 # sample, added once per visit
       hours: { min: 1, max: 8, step: 0.5, default: 2 }
     - id: "drain-cleaning"
       label: "Drain cleaning"
       mode: "units"
       unit: { one: "drain", other: "drains" }
       base: 79 # sample
       perUnit: 50 # sample
       units: { min: 1, max: 6, step: 1, default: 1 }
   ```

   The yearly maintenance plans are in the same file, under `plansSection`.

   Every number in this file is a sample: replace them all with your own rates. Copy the same numbers into the file of every other language, such as `src/content/pricing/french/-index.md`: `npm run build` warns when they differ. The currency is `currency` under `[settings.estimator]` in `config.toml` (default `USD`).

   The services themselves are one file each in `src/content/services/english/`, with what each visit includes. Details: [Pricing & Estimator](/plumbo/customization/pricing-estimator/) and [Services & What's Included](/plumbo/customization/services-included/).

5. **Replace the sample service areas**

   The four areas in `src/content/areas/english/` (North Harbor, Elm Park, Westfield Heights, Old Mill) are fictional. Rename one file per real area and set its postal codes:

   ```yaml
   title: "North Harbor"
   zips: ["55501", "55502", "55503"] # sample
   neighborhoods:
     - "Harbor Point"
   ```

   The area finder matches visitors against `zips`, `neighborhoods`, and `aliases`; the booking form checks the postal code against `zips`. The footer areas column lists your area files on its own. The header **Areas** menu is a plain list: update its links and the count in **All areas (4)** in each `src/config/menu.<language>.json`. If your postal codes are not 5 digits, change `zipPattern` under `[settings.booking]` in `config.toml` (the comment there has a UK example). Details: [Service Areas](/plumbo/customization/service-areas/).

6. **Set your brand colors**

   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: #c2410c; /* text orange: links, icons, checks */
     --theme-accent: #cf4510;  /* pill buttons */
     --theme-deep: #cf4510;    /* the orange block: stats band, emergency band */
     --theme-forest: #0f1e33;  /* navy: dark blocks and dark footers */
   }
   ```

   Change the matching lines in `:root.dark` too, then check both modes with the light/dark button in the header. Details: [Colors & Fonts](/plumbo/customization/colors-fonts/).

7. **Add your logo**

   Plumbo draws a built-in mark (an orange tile with a white water drop) next to `logoText`. To use your own logo file instead, put it in `public/` or `src/assets/images/` and set it in `[site]`:

   ```toml
   [site]
     logo       = "/images/my-logo.svg"
     logoText   = ""      # empty if your logo already has the name in it
     logoWidth  = "116px"   # your logo's width at 28 px tall
     logoHeight = "28px"
   ```

   Then set `[site.favicon] image` to a square version of your logo and, with `npm run dev` running, run `npm run generate-favicons`. Details: [Site Identity & Logo](/plumbo/customization/site-identity-logo/).

8. **Connect the forms**

   The contact form and the booking form 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.com"
     contactFormProvider = "formsubmit.co"   # formsubmit.co | formspree | netlify

   [settings.booking]
     formAction = ""   # empty sends booking requests to contactFormAction
   ```

   The newsletter sign-up needs your Mailchimp address in `formAction` under `[settings.subscription]`. Details: [Forms](/plumbo/customization/forms/) and [Booking Request](/plumbo/customization/booking-request/).

9. **Replace the photos**

   The sample photos are in `src/assets/images/`, grouped by area (`heroes/`, `services/`, `areas/`, `projects/`, `team/`, and so on). Content files point at them with paths that start with `/images/`:

   ```yaml
   image: "/images/services/leak-detection.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](/plumbo/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 (step 8), and `[pricing]` means the price files of your languages differ (step 4). Then follow the [Deployment](/plumbo/deployment/) guide, which has the full launch checklist.

</Steps>

### What Next?
- Pick your homepage: Plumbo has four (`/`, `/home-residential/`, `/home-water/`, `/home-commercial/`). See [Homepages](/plumbo/customization/homepages/).
- Only need English? See [Internationalization](/plumbo/customization/internationalization/).
- Point the header button and menus at your pages, and hide the **Pages** demo menu: [Header](/plumbo/customization/header/) and [Menus](/plumbo/customization/menus/).
- Replace the demo content page by page: [Pages](/plumbo/customization/pages/) lists every page and its file. Update the coupons and financing terms on `/specials/`: [Emergency & Specials](/plumbo/customization/emergency-specials/).
- Replace the sample reviews and projects: [Reviews & Projects](/plumbo/customization/reviews-projects/).
- Try the other layouts of your sections: [Section Layouts](/plumbo/customization/section-layouts/).
- Let an AI assistant do the repetitive work: [Prompt Library](/plumbo/ai-customization/prompt-library/).