> For the complete documentation index, see [llms.txt](https://docs.divisupply.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.divisupply.com/crest/change-color-scheme.md).

# Change Color Scheme

Crest uses Divi 5 Design Variables to manage the main colors used throughout the website. This means you can update the color scheme from one central place instead of editing every section and module individually.

### Open the Variable Manager

1. Open any page on your Divi site..
2. Click Enable Visual Builder.
3. In the Divi Builder sidebar, click the Variable Manager icon.
4. Open the Colors section to view the color variables included with Crest.
5. Update the **Primary** and **Secondary Color** with your own.

<div data-with-frame="true"><figure><img src="/files/z0QlTU0gTD9AqZizcw1T" alt=""><figcaption></figcaption></figure></div>

And that's it, this will replace all the colors across your site.


---

# 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://docs.divisupply.com/crest/change-color-scheme.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.
