> For the complete documentation index, see [llms.txt](https://storypress.gitbook.io/storypress-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://storypress.gitbook.io/storypress-docs/theme-and-setup/colors.md).

# Colors

Your theme’s **Colors** block defines the site-wide palette: navigation, footer, buttons, inputs, and main content. Set it once and every page follows.

***

## What you can set

**Nav & footer** — Background and text for the top nav (and mobile nav), and for the footer. So the header and footer always match your brand.

**Primary, secondary, tertiary** — Main accent colors used across the site (links, buttons, highlights). Many blocks use “Primary” by default so one change updates the whole look.

**Main content** — Background and text for the main area, plus optional “canvas” background. You can also choose a **light or dark tone** in the theme so defaults match your preference.

**Buttons & inputs** — Background, text, placeholder, and hover states for buttons and form fields. Keeps forms and CTAs consistent.

**Other** — Utility colors (e.g. red, green, black, white), thumbnail and lightbox colors when relevant.

***

## Tabs / groups

Colors are often grouped in tabs such as:

* **Nav / Footer** — Nav background/text, footer background/text, mobile nav.
* **Main content** — Main area and canvas.
* **Button / Input** — Form and button styling.
* **Thumbnail** / **Lightbox** — When those features use theme colors.

***

## Tips

* Set **primary** (and optionally secondary) first; many blocks use them for CTAs and links.
* Use the same color for nav background and footer background if you want a unified bar.
* Theme **tone** (light/dark) affects default text and background; set it to match your brand.


---

# 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://storypress.gitbook.io/storypress-docs/theme-and-setup/colors.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.