> 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/overview.md).

# Theme overview

Your **theme** is the single place in StoryPress where you set the look and feel of your entire site. Configure it first; then everything you build—pages, blocks, forms—will use these settings.

***

## What the theme controls

| Area                                                             | What you set                                                                                                                                        |
| ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**Fonts**](/storypress-docs/theme-and-setup/fonts.md)           | Google Fonts or Adobe Fonts (heading + paragraph), plus font weights for headings, body, buttons, inputs, and menus.                                |
| [**Colors**](/storypress-docs/theme-and-setup/colors.md)         | Site-wide palette: nav and footer (background + text), primary/secondary/tertiary, buttons and inputs, canvas and main content. Light or dark tone. |
| [**Navigation**](/storypress-docs/theme-and-setup/navigation.md) | Site-wide top navigation (menus and structure).                                                                                                     |
| [**Footer**](/storypress-docs/theme-and-setup/footer.md)         | Site-wide footer (links, socials, copy).                                                                                                            |
| [**Favicon**](/storypress-docs/theme-and-setup/favicon.md)       | Browser-tab icon, theme color, and optional PWA manifest (maskable icon, short name).                                                               |
| **Layout**                                                       | Optional max width for the main content area and for components.                                                                                    |

***

## Why set the theme first

* **Consistency** — One nav, one footer, one color and font system across every page.
* **Speed** — You’re not redoing colors or fonts block by block; you build content on a foundation that’s already set.
* **Brand** — Fonts and colors make the site yours before you add a single paragraph.

***

## Where to set it

In StoryPress, open your **theme** (often at the root of your content or in a “Theme” / “Global” area). You’ll see sections or tabs for:

* **Colors** — Nav/Footer, Main content, Button/Input, etc.
* **Fonts** — Embed codes (Google/Adobe) and weights.
* **Navigation / Footer** — Add your nav and footer blocks.
* **Preferences** — Site title, favicon, favicons (and related options).

The next pages in this section walk through [Fonts](/storypress-docs/theme-and-setup/fonts.md), [Colors](/storypress-docs/theme-and-setup/colors.md), [Navigation](/storypress-docs/theme-and-setup/navigation.md), [Footer](/storypress-docs/theme-and-setup/footer.md), and [Favicon](/storypress-docs/theme-and-setup/favicon.md) in more detail.


---

# 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/overview.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.