Brand Centre

Creating and editing themes

Use the Theme Editor to build a brand-correct theme — colours, fonts, logos, and a single default-flag toggle.

The Theme Editor is the form you'll spend most of your Brand Centre time in. It's deliberately small — a handful of fields — but each one ends up controlling something that participants will see across every public-facing surface Gleo produces.

This page walks the editor end-to-end. The "where this theme actually shows up" story is in Brand Centre overview; this page is about getting the theme itself right.

Video walkthrough — coming soon

What the editor lets you set

Name

A label for the theme. Show up in the theme list, in pickers, and as the inherited theme name on overrides.

Colours

A primary colour (required) and an optional secondary. Drives buttons, accents, headers, and links on themed surfaces.

Fonts

A heading font and a body font. Pick from web-safe stacks or any Google Font.

Logos

One or more uploads (PNG / JPEG / SVG / GIF, ≤ 5 MB each). You can add and remove logos from the same theme.

Plus one important toggle: set as default theme. One theme per company can carry the default flag.

Field-by-field

Name

A short, recognisable label. The theme list, all the pickers (template-level, playbook-level, session-level), and any "inherited from…" labels all refer to the theme by name — so make it something the team will recognise without having to open it. "Acme — Customer-facing" beats "Theme 3".

Colours

The primary colour is required; the secondary is optional. Together they drive accents and contrast on every themed surface. A few practical notes:

  • Pick a primary that has enough contrast against white text (for buttons) and against a white background (for accents). The editor doesn't enforce contrast — it's on you to test.
  • Skip the secondary unless you have a clear use for it. A single, strong primary is usually enough; a poorly-chosen secondary is worse than none.

Fonts

Heading font and body font, picked separately:

  • Web-safe — system stacks like Helvetica, Arial, Georgia, Times New Roman. Always available; render instantly with no extra fetch.
  • Google Fonts — anything from the Google Fonts library. Fetched on first render; cached for subsequent visits.

If you don't have a brand font, web-safe is fine. If you do, paste the Google Fonts name and let the editor pull it in. Heading and body can be the same family — there's no rule that says they must differ.

Logos

Logo upload is multi-upload: a single theme can carry multiple logos (e.g. a full-colour version, a monochrome version, a square mark). Public surfaces pick the variant that fits the context.

Constraint Limit
File types PNG, JPEG, SVG, GIF
Max size per file 5 MB
Max number per theme Multiple — add more by re-uploading

You can remove existing logos from the theme by clicking the remove control next to each upload.

Default theme

A single checkbox: Set as default theme. One per company. Covered in detail in Managing themes and the default — for now, leave it off if you're creating a one-off override theme; turn it on if this is the canonical brand theme for the whole company.

Walkthrough

  1. 1

    Open the editor

    Brand Centre → New theme. The editor opens to an empty theme.

  2. 2

    Name and primary colour

    Pick a clear name. Set the primary colour. The editor updates the preview as you type.

  3. 3

    (Optional) secondary colour

    Add a secondary if your brand uses one. Skip if not — the primary alone is usually plenty.

  4. 4

    Pick fonts

    Heading and body, web-safe or Google Fonts. The preview re-renders to use them.

  5. 5

    Upload one or more logos

    Drop in PNG / JPEG / SVG / GIF files, each ≤ 5 MB. Watch the upload toast — see the pitfall below.

  6. 6

    (Optional) set as default

    If this theme should be the company-wide fallback, tick Set as default theme. Any previous default is automatically un-defaulted.

  7. 7

    Save

    Save the theme. It now appears in the theme list and is selectable in every theme picker (Playbook Template, Playbook, Session Template, Session).

Tips & pitfalls

Watch the upload toast for oversized logos. The 5 MB-per-logo cap is enforced server-side. If you drop in a file that's over the limit, the upload fails — but the in-page state can momentarily look like it succeeded. The toast notification is the source of truth: if you don't see a success message, the file didn't make it. Re-export the logo at a smaller size and try again.

SVG beats PNG for logos with text. SVG renders crisply at every size; PNG starts looking soft on retina displays at larger sizes. If you have an SVG version of your logo, prefer it.

Test the primary colour against a button. The single most-visible use of the primary is on call-to-action buttons. Open the public prep page after saving and check that text on a primary-coloured button is readable.

Related pages

Concept Brand Centre overview Action Managing themes and the default Concept Theme inheritance