# Rebranding the Marketing Site

> Change the copy, links, FAQ, legal text, logo and colours of the marketing pages without touching kit code.

*Canonical: https://makerkit.dev/docs/void-cloudflare/marketing/rebranding*

---

Everything a visitor reads on the marketing pages comes from files you own. You rebrand by editing them; the components stay as they are.

This page is part of the [Marketing documentation](./overview).

## The Brand Pass

Put your brand in every file at once with `pnpm kit:brand` (an agent uses the `kit_brand` tool). It reads `brand.json` at the project root, which your agent writes from your answers:

```json
{
  "productName": "Acme",
  "logo": "brand/logo.svg",
  "logoDark": "brand/logo-for-dark-mode.svg",
  "primaryColor": "#4f46e5",
  "sender": "Acme <hello@acme.com>",
  "salesEmail": "sales@acme.com",
  "legal": { "company": "Acme Ltd", "address": "1 Main St, London", "email": "legal@acme.com" }
}
```

- Only `productName` is required; anything left out is left as it is.
- `logo` and `logoDark` are files in the project (save them in `brand/`): SVG, PNG or WebP, at most 512 KB. A JPG won't do (save it as PNG). An SVG with scripts, event handlers or links to other files is refused: export a plain SVG or use a PNG.
- `logoDark` is the version shown **in** dark mode, usually a white or light logo. Leave it out and `logo` shows in both modes.
- `sender` must be on a domain you own: a Gmail, Outlook or iCloud address can't send email for your app.

In the Makerkit Console, a form saves `brand.json` for you (the `kit_brand_save` tool: it checks every field and the logo first, writes the logo to `brand/logo.<type>` and `brand/logo-for-dark-mode.<type>`, and writes nothing on a problem), then applies it with `kit_brand`. The form opens with what's saved (`kit_brand_read`), so you change only what you want.

`pnpm kit:brand --plan` shows each change first, `--yes` makes them, and running it again changes nothing. Change a value in `brand.json` and run it again: it replaces what it wrote last time, which it records in `brand.lock.json` (commit both).

| `brand.json` | What it writes |
|---|---|
| `productName` | `PRODUCT_NAME` in `apps/web/.env` (the live app gets its own in the deploy steps: `pnpm --filter web exec void secret put PRODUCT_NAME`) and `[Product name]` in the legal pages |
| `logo`, `logoDark` | `apps/web/public/images/logo.*` / `logo-dark.*` and `apps/web/config/logo.config.ts` (earlier logo files are removed; the plan lists them) |
| `theme` | optional: a ready-made look, by id (`kit_brand_read` lists them, e.g. `graphite`, `nature`, `mono`; `default` is the one the kit ships). Sets the colours (light and dark mode) and the corner radius in `apps/web/styles/theme.css`. The looks other than `default` are tweakcn's presets (Apache 2.0) |
| `primaryColor` | `--primary` and its text colour in `apps/web/styles/theme.css`, light and dark mode (a dark colour gets a lighter shade in dark mode so it stays visible); with a `theme`, it replaces that look's main colour |
| `sender` | `email.from` in `apps/web/void.config.ts` |
| `salesEmail` | the `mailto:…@example.com` "Contact sales" links in `apps/web/config/billing.config.ts` (an address you set by hand is left alone; the plan says so) |
| `legal` | `[Company name]`, `[address]`, `[email address]` and `[date]` in `apps/web/content/legal/*.md` |

Your own favicons, the link-preview picture and the legal pages' own sections stay yours: `pnpm kit:doctor --launch` lists them.

### After a Kit Update

`kit:brand` edits files the kit also updates (`styles/theme.css`, `void.config.ts`, `config/billing.config.ts`, `config/logo.config.ts`, `content/legal/*.md`). On a merge conflict in one of them, take the kit's version, then run `pnpm kit:brand --plan` and `--yes`: your `brand.json` puts your values back. Edits you made to those files by hand, beyond `brand.json`, are yours to redo.

## Before You Launch

Run `pnpm kit:doctor --launch` (or ask your agent: `kit_doctor` with `scope: launch`). It changes nothing and lists every placeholder the kit ships that would go live as is, with its file and line:

- example text and the warning box in the legal pages
- the `Makerkit <noreply@example.com>` email sender (`apps/web/void.config.ts`) and the "Contact sales" address (`apps/web/config/billing.config.ts`)
- the default product name (`PRODUCT_NAME`) and the Makerkit logo
- the Makerkit icons (browser tab, bookmarks, phone home screen) and no `og:image`, the picture a shared link shows

Each one is a step for you that says what to give your agent (your company's details, an address, a logo file) and which file it changes. Run it again afterwards: nothing left means you're ready.

## Product Name and Logo

- **Name:** `PRODUCT_NAME` (env). The landing page, FAQ and footer use it through `{productName}` in the messages; legal page titles come from their Markdown frontmatter.
- **Logo:** image files in `apps/web/public/images/` named in `apps/web/config/logo.config.ts` (`src`, and `darkSrc` for dark mode or `null`), shown by `apps/web/components/app-logo.tsx` in the header, footer, sidebar and sign-in pages. Set them with the brand pass above; placing a file by hand, `pnpm kit:doctor --launch` checks it the same way.
- **Icons:** `apps/web/public/favicon.ico` (browser tab) and `apps/web/public/images/favicon/` (`favicon-16x16.png`, `favicon-32x32.png`, `apple-touch-icon.png` at 180 × 180 for phone home screens). Replace the files and keep their names; they're linked on every page in `apps/web/void.config.ts` (`head.link`).

## Copy

All copy is in `apps/web/messages/<locale>/marketing.json`:

| Keys | Where it shows |
|---|---|
| `nav.*`, `header.*` | Header links and buttons |
| `landing.title`, `landing.description` | The landing page's `<title>` and meta description |
| `landing.pill.*`, `landing.hero.*` | The hero: pill, two-line headline (`title`, `highlight`), subtitle, buttons |
| `landing.features.*` | The features grid (`/#features`) |
| `landing.cta.*` | The closing call to action |
| `faq.*` | The FAQ page, its teaser on the landing page, and its `<title>` |
| `footer.*`, `legal.*` | Footer description, copyright, column headings and legal link labels |

Rich text uses tags, e.g. `"<b>Passkeys</b> and magic links"` renders the tag through `t.rich`; never HTML. Edit them by hand or with the `app_translations_*` MCP tools.

## Links

Header links, footer columns and legal links are in `apps/web/config/marketing-navigation.config.ts`. Labels are message keys; paths are site paths or `https://` URLs. Details: [Marketing Navigation](../configuration/navigation#marketing-navigation).

## Features Grid

The landing page's grid is `apps/web/components/landing-features.tsx`: six tiles built from the bento primitives in `@kit/ui/marketing`. Change a tile's text in `landing.features.*`; change what a tile shows, or add a tile, in that file. Illustrations are icons and shapes only, so they work in any language.

## FAQ

Questions and answers are `faq.items.<id>.question` and `.answer` in `marketing.json`. Their order, and how many the landing page shows (`FAQ_TEASER_COUNT`), are in `apps/web/config/faq.config.ts`. `/faq` also publishes them as schema.org FAQPage JSON-LD for search results.

Every id in `faq.config.ts` needs a question and an answer in the default locale (other locales fall back to it); a missing one renders as its key.

## Legal Pages

The privacy policy, terms and cookie policy are Markdown in `apps/web/content/legal/`. Each starts with a `> [!WARNING]` callout saying it's a placeholder: replace the text, reviewed by a lawyer, and remove the callout before you launch. The page title and meta description come from the frontmatter (`title`, `description`).

The cookie policy lists the cookies the kit sets (session, `locale`, `theme`). If you add analytics or other cookies, list them too, and ask for consent where the law requires it: the kit ships no consent banner.

## Colours and Components

The pages use theme tokens only (`primary`, `foreground`, `muted`, `border`): change `apps/web/styles/theme.css` and the marketing site follows, in light and dark mode. Hover glows, lines and halos in the features grid use `primary`.

### Components

`@kit/ui/marketing` exports the building blocks: `SiteHeader`, `SiteFooter`, `Hero`, `Pill`, `CtaButton`, `PrimaryCtaButton`, `SecondaryCtaButton`, `CtaBand`, `FaqList`, and the bento primitives (`BentoGrid`, `BentoTile`, `BentoSectionHeader`, `IconNode`, `Lines`, `Toast`, `Timeline`, `Halo`). They're presentational: links and text arrive as props, so a page composes them with its own copy.

---

**Next:** [Adding a Page →](./adding-a-page)
