> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/branding-and-onboarding/choosing-your-sites-color-palette.md).

# Choosing your site's color palette

{% embed url="<https://doctorlogic.wistia.com/medias/pj023lb5z0>" %}

When choosing a color palette for your website, it's important to consider your brand's personality and the emotions you want to evoke in your audience. You can start by selecting a primary color representing your brand, then choose 2-3 additional colors to complement it. You can also use tools such as Adobe Color or Coolors (<https://coolors.co/>), which allow you to generate color schemes based on a specific color or create color schemes from scratch. Additionally, you should also keep in mind accessibility concerns, making sure that the colors you choose have enough contrast to be easily read by people with visual impairments.

**Check out these resources for an in-depth look at color psychology:**

{% embed url="<https://doctorlogic.com/blog/medical-logo-colors.html>" %}

{% embed url="<https://www.helpscout.com/blog/psychology-of-color/>" %}

{% embed url="<https://coschedule.com/blog/color-psychology-marketing>" %}

**If you would like to do a full overhaul to rebrand your site, contact your Customer Success Manager to discuss a website redesign package!**&#x20;

{% content-ref url="/pages/Hkecq1Ax8z1BewLgMH0U" %}
[The Customer Success Manager](/docs/contact-support/the-customer-success-manager.md)
{% endcontent-ref %}


---

# 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://help.doctorlogic.com/docs/branding-and-onboarding/choosing-your-sites-color-palette.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.