Quick Start

Make Consultiz Yours In 30 Minutes

Skill level: Beginner · Time: 30 minutes · You need: the site running with npm run dev (Installation)

This page walks through the changes almost every firm needs, in order. Each step names the file and the lines to edit. Save the file and the browser shows the change.

Name your site and set its address

Open src/config/config.toml and edit the [site] block:
```
[site]
  title       = "Acme Advisory"
  description = "Tax, accounting, and business advisory for growing companies."
  tagline     = ""   # empty uses common.tagline from src/i18n/en.json and fr.json
  baseUrl     = "https://www.example.com"
```
Change the tagline in each language under common.tagline in src/i18n/en.json and fr.json. baseUrl is your live address. It ships empty, and npm run build prints a [site] warning until you set it. Canonical links, the sitemap, robots.txt, the RSS feeds, llms.txt, and social previews all use it. Restart npm run dev after you change it.
Decide on languages

Every page ships in English and French. If you only need English, set enable = false under [settings.multilingual] in the same file, then restart npm run dev. The French files stay on disk but are no longer built. See Internationalization to remove them for good.

Add your logo and favicon

Put your logo files in src/assets/images/ and point [site] at them:

[site]
  logo          = "/images/logo.svg"        # on light backgrounds
  logoLight     = "/images/logo-light.svg"  # on dark footers
  logoAlternate = "/images/logo-light.svg"  # on transparent headers over images
  logoText      = "Acme Advisory"           # set to "" if your logo already contains the name

Then set [site.favicon] image to a square version of your logo and run npm run generate-favicons. Details: Site Identity & Logo.

Set your brand colors

Open src/styles/theme.css and change the two brand colors in the @theme block:
```
--color-primary: #CCF664;  /* buttons, highlights */
--color-accent: #0f3d3a;   /* deep accent color */
```
Details: Colors & Fonts.
Replace the demo contact details

The theme ships with sample contact details ([email protected], a placeholder phone number, a sample office list). Replace them in config.toml:
- [settings.contactInfo]: phone, email, address, and opening hours used in footers and the contact drawer
- [settings.headerTopBar]: the email and phone in the header top bar
- [settings.officeDropdown]: the Our office list in the top bar (set enable = false if you have one office)
The address and hours in the top bar fall back to src/content/sections/english/home-header.md (and french/). The contact page has its own details in src/content/contact/english/-index.md. PUBLIC-VALUES-NEEDED.md in the theme lists every demo value.
Write your homepage banner

The homepage slider is src/content/sections/english/banner-slider.md. Change each slide’s tag, title, shortInfo, features, and bgImage. Do the same in src/content/sections/french/banner-slider.md if you kept French. To change the banner on the homepage only, use the corporateBanner block in src/content/homepage/english/-index.md instead (How Consultiz Works).
Point the menus and the header button at your pages

The header button is in config.toml:
```
[settings.navigationButton]
  enable = true
  label  = ""          # empty uses navigation.buttonLabel from src/i18n/en.json
  url    = "/contact/"
```
The menu links are in src/config/menu.en.json (and menu.fr.json). The Home and Who we are menus link to every demo page, so most firms shorten them. Details: Menus.

Connect the forms

No form sends anything until you connect it. In config.toml:

[settings]
  contactFormAction   = "https://formsubmit.co/[email protected]"
  contactFormProvider = "formsubmit.co"   # formspree | formsubmit.co | netlify

[settings.subscription]
  formAction = "https://example.us21.list-manage.com/subscribe/post?u=...&id=..."

The standalone newsletter section has its own endpoint, formAction in src/content/sections/english/newsletter.md. Details: Forms.

Change the footer text and social links

The footer description and copyright line are under footer in src/i18n/en.json (and fr.json). The copyright text is plain text, so update the year yourself. The homepage footer has its own file, src/content/sections/english/footer-newsletter-grid.md. Social links are in src/config/social.json; they all ship disabled.
Check and build

Stop the dev server, then run:
Terminal window
```
npm run astro-check
npm run build
```
Fix anything astro-check reports. If the build prints a yellow [site] warning, baseUrl is still empty (step 1). Then follow the Deployment guide.

What Next?

Replace the demo content page by page: Pages lists every page and its file.
Pick the homepage you want as your main one: Homepages.
Learn how sections and page overrides work: Sections.