> For the complete documentation index, see [llms.txt](https://acoservice.gitbook.io/acoservice-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://acoservice.gitbook.io/acoservice-documentation/running-your-aco/branding.md).

# Branding

Colours, logo and wording — your members never see ACO Service.

**Branding** on any ACO in your console opens the same editor platform staff use, with a live preview beside it.

## What you control

|                    |                                                                                                  |
| ------------------ | ------------------------------------------------------------------------------------------------ |
| **Colours**        | 12 fields — primary, secondary, tertiary, backgrounds, cards, borders. 10 presets to start from. |
| **Logo**           | Any image URL. Hosted anywhere — your CDN, Discord, S3.                                          |
| **Favicon**        | The browser-tab icon. Falls back to your logo if you skip it.                                    |
| **Name**           | Shown as two halves. The second is painted in your accent colour.                                |
| **Tagline**        | Under your name on the landing page and in the browser tab.                                      |
| **Discord embeds** | Colour and footer for the messages your bot sends.                                               |
| **Default theme**  | Whether members land in light or dark.                                                           |

## Your name comes in two halves

"Santah's" + "Grotto", or "Acme" + "Cards". The **second half is painted in your accent colour** everywhere it appears — navbar, footer, dashboard, browser tab.

If you put the whole name in the first field, it renders correctly but entirely in one colour, and you lose the accent. Splitting it is what makes the wordmark look designed.

## Your colours drive the whole site

The palette is not decoration around a fixed theme — your primary colour becomes the accent across every surface your members see: buttons, links, highlights, the bot's embeds.

{% hint style="info" %}
**Your accent is adjusted for legibility, not overridden.** If the colour you choose already has enough contrast against the background, it is used exactly as you entered it. If it does not, it is nudged until text on it is readable — starting from *your* colour rather than a generic one. A deliberately muted brand stays muted.
{% endhint %}

## Preview, then publish

Changes save immediately and appear on your site straight away.

If your ACO is a **draft**, only you can see any of it, so you can iterate freely. If it is **live**, changes are public the moment you save — so if you are making a big change to a running site, consider [unpublishing](/acoservice-documentation/running-your-aco/preview-and-publish.md#unpublishing) first.

## Your members never see ACO Service

No ACO Service logo, name or link appears anywhere on your site. Your favicon is yours. Your bot carries your name.

The only place ACO Service's own mark appears is on ACO Service's own surfaces — the marketing site and this console.

## If your logo does not appear

| What you see                         | What it means                                                                       |
| ------------------------------------ | ----------------------------------------------------------------------------------- |
| **A coloured square with a letter**  | No logo URL saved. That square is the fallback, using your accent and initial.      |
| **A broken image**                   | The URL is not publicly reachable. Paste it into a private browser window to check. |
| **Platform icon in the browser tab** | No favicon *and* no logo saved. Setting either fixes it.                            |
| **Name renders in one colour**       | The whole name is in the first field — split it to get the accent.                  |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://acoservice.gitbook.io/acoservice-documentation/running-your-aco/branding.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.