> 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/customisation/rebranding.md).

# Rebranding

Making Hollow Peak look like your company.

Almost everything a visitor recognises as “your company” is a setting. You should not need to edit code to rebrand.

## The checklist

### 1. Name and logo

**Site Management → Identity & Content**

* Site name — header, footer, dashboard sidebar, page titles, email sender
* Tagline
* Logo
* Favicon
* Link preview image

### 2. Colours and type

**Site Management → Appearance**

Colour tokens, fonts, radii, glass effects, background.

### 3. Contact details and social links

Same screen as identity. They appear in the footer, and only when filled in.

### 4. Footer

The about paragraph and copyright line.

### 5. Navigation

**Site Management → Navigation**

### 6. Email identity

**Site Management → Email** — the from name and address recipients see.

### 7. Content

**Site Management → Pages** — rewrite the shipped pages in the page builder.

### 8. Store

**Store → Settings** — currency, and the menu label if “Shop” is not your word.

## What stays

{% hint style="info" %}
You may rebrand the **application** as far as you like — that is what the licence is for.

You may not remove copyright notices from source files, or claim authorship of Hollow Peak itself. Rebranding the product you operate and claiming to have written the software are different things.

See `legal/LICENSE.txt`.
{% endhint %}

## The dashboard

The dashboard follows the same theme and the same logo, so staff see your brand too.

## Beyond settings

For layout changes rather than colour changes, see **Custom CSS & JavaScript**.


---

# 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/customisation/rebranding.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.
