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

# Appearance & Theme

Colours, fonts and the overall look.

**Site Management → Appearance**

Changes preview live. Nothing is public until you publish.

## Presets

Start from a preset, then adjust. It is quicker than building a palette from nothing.

## Colours

| Token                        | Used for                       |
| ---------------------------- | ------------------------------ |
| **Background**               | The page behind everything     |
| **Background 2**             | Panels and raised surfaces     |
| **Panel** / **Panel strong** | Cards, with their glass effect |
| **Line**                     | Borders and dividers           |
| **Text**                     | Body copy                      |
| **Muted**                    | Secondary text, captions, help |
| **Primary**                  | Buttons, links, highlights     |
| **Primary strong**           | Hover states and emphasis      |
| **Secondary**                | Gradients paired with primary  |
| **Highlight**                | Badges and accents             |
| **Link**                     | Inline links                   |

{% hint style="warning" %}
**Check contrast.** A pale primary on a pale background looks refined and is unreadable. Aim for at least 4.5:1 between text and its background.
{% endhint %}

## Appearance controls

| Control              | Effect                               |
| -------------------- | ------------------------------------ |
| **Radius**           | Corner rounding on inputs and panels |
| **Button radius**    | Buttons specifically                 |
| **Card radius**      | Cards specifically                   |
| **Glass opacity**    | How solid panels are                 |
| **Glass blur**       | Backdrop blur behind panels          |
| **Shadow intensity** | Depth                                |
| **Base font size**   | Scales the whole interface           |

## Fonts

Pick a heading font and a body font. The picker offers Google Fonts, loaded only when you choose one — a site left on the system stack requests nothing.

Two families is usually the limit before a site looks busy. The same font for both, differing in weight, is a safe choice.

## Background

**Default** — the theme background colour.

**Gradient** — between two colours you choose.

**Image** — from the media library, with an overlay so text stays readable.

## Light and dark

Hollow Peak ships both. Visitors get a switch in the header, and their choice is remembered.

The switch can be removed if you want one fixed appearance — the toggle at the bottom of this screen.

With no stored choice, a visitor follows their operating system setting.

## Publishing

**Publish** applies your changes to the public site. Until then only you see them.

**Reset** returns to the shipped defaults.

Every published change is versioned and can be rolled back from the history.

## Going further

The theme system covers colour, type and shape. For layout changes, see **Customisation → Custom CSS**.


---

# 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://hollow-peak.gitbook.io/docs/website-and-cms/appearance-and-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.
