> For the complete documentation index, see [llms.txt](https://wpdocs.gitbook.io/bookory/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wpdocs.gitbook.io/bookory/setting/color.md).

# Color

**Step 1** - you can go to any elementor edit page.

![](/files/w5tHmRaltsIYxQRUkSoM)

**Step 2** - Site Settings >> Global Colors&#x20;

![](/files/AJSAQKBaYAOgY3Ct1N9W)

**Step 3** - Settings color for your site

1. **Primary Color** is the main color of your site.

* Regular: original color
* Hover : color when hover items

Example: Color Button , Color Link and some other places.

2\. **Body Color** is color of the content text.

Example: Color content, description ... in single blog, single product, page ...

3\. **Heading Color** is color of heading text.

Example: Color Title , Title Tab ...

4\. **Border Color** is color border block.

Example: border product block, border form input and places with borders ...

5\. **Light Color** is color light used for sub description.

Example: Color categories, color date time, color subtitle ...

Note: Color is sometimes used for many special places to see which colors apply correctly to what cases you can select and test.


---

# 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://wpdocs.gitbook.io/bookory/setting/color.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.
