> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/branding/brand-guidelines-detail-page.md).

# Brand Guidelines Detail Page

The Brand Guideline Detail page displays the full structure and content of a brand guideline, including sections like logo, colors, typography, and more. The specific elements displayed in your branding sets will vary depending on how your brand guidelines are defined. It allows users to view, edit, and manage brand identity rules in one centralized place. Each element can be a section:

<table><thead><tr><th width="176">Sections</th><th>Definitions</th></tr></thead><tbody><tr><td><strong>Logo</strong></td><td>Your brand's logo is usually the most prominent element, setting the visual foundation for your brand identity.</td></tr><tr><td><strong>Color Palette</strong></td><td>The colors approved for use in your branding will be clearly defined. This ensures consistent color application across all your digital assets.</td></tr><tr><td><strong>Fonts</strong></td><td>The specific fonts designated for your brand will be listed. This helps maintain a consistent brand voice and visual style in all your content.</td></tr><tr><td><strong>Images</strong></td><td>The set of images approved for use</td></tr></tbody></table>

* Brand guidelines are divided into sections for easy management.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FGocHje7V1tN9PCRszwzF%2FGroup%20802%20(1).png?alt=media&amp;token=208e040a-d59b-4fcc-aef6-cf23c05d4000" alt=""><figcaption></figcaption></figure>

### **Display options**

* In the **Settings**, enable **"Use New Display"** to switch to the new layout for viewing the guideline.
* You can also enable **"Hide Tabs"** to hide navigation tabs and simplify the viewing interface.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FIS81PVQXTuGJKABqafDw%2FGroup%20809%20(1).png?alt=media&amp;token=684e3955-9167-44a2-b616-45f683f9a432" alt=""><figcaption><p>Display options </p></figcaption></figure>

* Some interfaces display according to options:

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FnO1D3Y7O22H14QW7posg%2FGroup%20810%20(1).png?alt=media&amp;token=73fb4fee-789d-469c-b967-7f111654d072" alt=""><figcaption><p>Hide tab section</p></figcaption></figure>

### **Reorder section**

Reorder the sections by **clicking/dragging** the sections below. You may **remove sections** by using the **✖** button.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FQcWLoiEo9GWJWcEdAT4g%2F0519_2_.gif?alt=media&amp;token=566131ba-e50d-46b0-9cd1-5e73bbf65633" alt=""><figcaption><p>Reorder section </p></figcaption></figure>

If you have any questions, don't hesitate to ask, we're always here to help!


---

# 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://support.hivo.co/branding/brand-guidelines-detail-page.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.
