> For the complete documentation index, see [llms.txt](https://visionstore.gitbook.io/visionstore-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visionstore.gitbook.io/visionstore-docs/scripts/badges/configuration/theme.md).

# Theme colours

Recolour the panels around the badges from config/theme.lua.

`config/theme.lua` colours the **panels around the badges**: the caption under a shown badge, the issuing review panel and the Badge Studio. The badges themselves have their own colours (set per badge, see [Designs and logos](/visionstore-docs/scripts/badges/configuration/designs.md#colours)).

```lua
Config.Theme = {
    accent = '#c4122f',         -- buttons, active tabs, timer bar
    accentHover = '#e01c3c',
    accentText = '#ffffff',     -- text on accent buttons
    text = '#e7dbbe',           -- main text
    muted = '#a69e8d',          -- secondary text
    background = '#0d0f12',     -- panel background
    surface = '#151518',        -- cards and inputs
    control = '#202022',        -- secondary buttons
    border = '#e7dbbe',         -- lines (drawn with low opacity)
    success = '#c7d7b0',        -- "VALID" status
    danger = '#ff8c9c',         -- "REVOKED" / "INACTIVE" status and errors
    revokedStamp = '#b10f2a',   -- stamp printed on void badges
    issuedStamp = '#276438',    -- stamp printed when a badge is issued
}
```

| Key            | Default   | Used for                                 |
| -------------- | --------- | ---------------------------------------- |
| `accent`       | `#c4122f` | Buttons, active tabs, timer bar          |
| `accentHover`  | `#e01c3c` | Buttons under the mouse                  |
| `accentText`   | `#ffffff` | Text on accent buttons                   |
| `text`         | `#e7dbbe` | Main text                                |
| `muted`        | `#a69e8d` | Secondary text                           |
| `background`   | `#0d0f12` | Panel background                         |
| `surface`      | `#151518` | Cards and inputs                         |
| `control`      | `#202022` | Secondary buttons                        |
| `border`       | `#e7dbbe` | Lines (drawn with low opacity)           |
| `success`      | `#c7d7b0` | "VALID" status                           |
| `danger`       | `#ff8c9c` | "REVOKED" / "INACTIVE" status and errors |
| `revokedStamp` | `#b10f2a` | Stamp printed on void badges             |
| `issuedStamp`  | `#276438` | Stamp printed when a badge is issued     |

{% hint style="success" %}
Colours must be 6-digit hex values (`#rrggbb`).
{% endhint %}

{% hint style="info" %}
Theme changes apply after `restart vision_badges`.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://visionstore.gitbook.io/visionstore-docs/scripts/badges/configuration/theme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.