> For the complete documentation index, see [llms.txt](https://docs.navless.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navless.ai/building-interactive-demos/tour-centers/editing-styles.md).

# Editing Styles

Style your Tour Center to your brand!

With Tour Center Style Editing you can...

<figure><img src="https://67180079-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKaMCOI4HEb21AIKZlkHe%2Fuploads%2FJ40pRIeLLDGw3tT810uw%2FScreenshot%202023-11-28%20at%2010.50.54%E2%80%AFAM.png?alt=media&amp;token=8c5d5df1-cf57-4b0c-9727-05bdcf0a7571" alt=""><figcaption></figcaption></figure>

* Add a logo
  * recommended a logo size of at least 64px x 64px
* Set a font&#x20;
* Enable light or dark effect&#x20;
  * toggle between light and dark effects which set container backgrounds automatically
* Set highlight & gradient colors
  * highlight sets most accent colors throughout the tour center - like the prompt button, icons, and container outlines
  * gradient affects the main CTAs (both Save & Share and the upper right button) - you may set a gradient or choose a solid color
* Upload background images/set color&#x20;
  * set color/overlay and/or upload a background image
* Customize component borders&#x20;
  * set in px for small and large buttons, containers, and more


---

# 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://docs.navless.ai/building-interactive-demos/tour-centers/editing-styles.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.
