For Website Developers

Website Brand

Declare your logo, colors, and title in r2ware.toml

Website Brand

Your website's brand — title, logo, icon, artwork, and primary color — is used everywhere the platform speaks on your behalf:

  • Platform pages on your domain — shopping cart and member login screens served on your own domain use your brand instead of the default r2ware look.
  • Notification emails — access grants, form notifications, and other platform emails carry your logo and primary color.

You declare it once, in your source repo, with a [brand] section in r2ware.toml.

The [brand] section

r2ware.toml is the platform-level config file at the root of your website's source folder (next to _config.yml) — the same file that controls the placeholder page. Add a [brand] section:

# src/r2ware.toml
[brand]
title = "Acme Co."
icon = "/assets/logo/icon.svg"
logo = "/assets/logo/logo.png"
artwork = "/assets/imgs/opengraph-art.jpg"
primary_color = "#67c3f3"
Key Type Meaning
title string Your brand name. Shown where a logo isn't (e.g. email header fallback).
icon string Small square mark (favicon-style). SVG or PNG.
logo string Full logo. Emails display it up to 200px wide.
artwork string Large hero/social image (e.g. your OpenGraph art).
primary_color string Hex color for buttons, headings, and accents (e.g. "#67c3f3").

All keys are optional, but the section is all-or-nothing: as soon as any [brand] key is set, it is your website's complete brand. Keys you leave out are simply unset — they are never filled in from anywhere else. Declare everything you want shown.

Values are literal strings — r2ware.toml is not run through Liquid, so {{ site.data.brand.logo }}-style references won't work. Write the actual path or URL.

Image values

Each image key accepts either form:

  • A site path like /assets/logo/logo.png — the file must exist in your built website output. At publish time the platform uploads it to the CDN and records the permanent URL, so receipts and emails keep working even off your domain.
  • An absolute URL like https://example.com/logo.png — used as-is.

If a site path doesn't resolve to a real file in the build, that key ends up unset — check the file's published location if an image doesn't appear.

Publishing and verifying

Brand values are read from your live published build — committing alone isn't enough. After editing r2ware.toml:

  1. Commit and publish your website.
  2. In the dashboard, open your website's Settings → Brand tab. It shows the brand exactly as the platform resolved it: your title, a color swatch, and image previews. Anything you didn't set reads not set.
  3. Use Preview sample email on that tab to see your brand on the email layout, and — if you've added a receipt layout — Preview sample receipt for the receipt.

If the Brand tab shows "Default brand in effect", your live build declares no brand at all and the platform's default r2ware brand is used on receipts, emails, and platform pages until you publish one.

Minimal example

A logo and a color are enough for most websites (remember to include title — with [brand] set, it won't be picked up from anywhere else):

[brand]
title = "Acme Co."
logo = "/assets/logo/logo.png"
primary_color = "#67c3f3"

Troubleshooting

  • Changes don't show up — brand comes from the live published build. Publish, then re-check the Settings → Brand tab.
  • A logo/icon/artwork reads "not set" — the path didn't match a file in the built output. Confirm the published file's URL on your live website and use that path.
  • Title or color missing after adding [brand] — the section is all-or-nothing; add title and primary_color to the section rather than relying on other config.
  • Broken image on the Brand tab — the recorded URL no longer serves the file (e.g. it pointed at an external host that moved). Switch to a site path so the platform hosts a copy on the CDN.