How to brand a site

Goal

Apply colors, font, logo, and default appearance to one selected site so the live reader matches the dashboard preview.

Conditions

• You are a workspace owner or admin. Editors and viewers can see the result only.
• You have already chosen which site in the Branding panel to change.
• If you want candidates from a repository, GitHub is connected under Sources. *(see How-to: How to connect a source)* *(see How-to: How to invite teammates)*

Procedure

1. In Branding, select the site. Set a primary and secondary color with the swatch or a six-digit hex value. Primary drives buttons and main accents. Secondary drives links and supporting accents. Font, legal link, and logo apply only to that site.
2. If you want reviewed candidates from GitHub, choose one connected repository and scan it. The scan is pinned to a commit and reads a bounded allowlist of static CSS, token JSON, package metadata, and passive logo paths. It does not execute repository code, install dependencies, or run build tools. Nothing is selected automatically.
3. Choose the values you want. Inspect the preview (button, link, badge). The preview uses the same color derivation the live site serves.
4. Pick the default appearance: light, dark, or match the reader device. Readers can still switch later.
5. Save. The apply step re-verifies pinned files before writing.

Verification

Open the site subdomain. You should see the new theme without republishing content. Branding and content are independent.

Failures

• Scan found nothing useful: the repository is outside the allowlist or has no static tokens. Set colors by hand.
• Apply rejected the pin: the commit moved or a file hash changed. Scan again, then choose candidates from the new pin.
• Editor cannot save: role is viewer or editor. An owner or admin must apply. *(see How-to: How to invite teammates)*