> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/knowledge-base/styling-and-customization.md).

# Styling & Customization

Customize the look and feel of your knowledge base

## Styling

Customize your knowledge base on its **Styling** settings page. See the preview change in real time as you update your configuration.

On the **Styling** tab, you can set:

* **Logos**: **Header Logo**, **Header Logo on Dark** (used in dark mode), and **Footer Logo**. Header and footer logos default to your Brand center logos.
* **Favicon**: defaults to your Brand center square logo.
* **Banner**: a default, image, or color background, with dark or bright text.

On the **Links** tab, you can set:

* **Header Links**
* **Footer Page Links**, grouped into sections
* **Footer Social Media Links**

Your primary and link colors come from **Settings > Workspace > Brand center > Colors**.

If your theme doesn't use a setting, it's marked **Not used by this theme**.

## General settings

In the knowledge base's **General** settings, you can also set:

* **Title**: used as the page's HTML title
* **Header**: the text at the top of your homepage, with a translation for each supported language
* **Knowledge Base URL subdomain**
* **Open Graph Image**: used in social link previews
* **Chat widget app**: which chat widget appears on the knowledge base, if you have more than one

## Custom Domain

Within the **General** settings of your knowledge base, you can specify a custom domain for your knowledge base. Examples of a typical subdomain are `help.yourcompany.com` or `support.yourcompany.com`.

## Collection icons

Give each collection a system icon or upload your own in the collection's settings. See Collections.

## Custom Code

Inject custom scripts from the **Code** settings page, under **Head Scripts**. For example, add a script for Google Analytics to collect page views or a tracking pixel to collect intent data from visitors.

When one of your custom themes is live, its scripts are managed in the theme editor instead. See [Custom themes](/pylon-docs/knowledge-base/styling-and-customization/custom-themes.md#scripts).

## Custom themes

Custom themes are available on the Enterprise plan. Manage them on the **Theme** tab of your knowledge base's **Styling** settings page.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FPsAufQkKZ42LBJTkUYBp%2FCleanShot%202026-05-12%20at%2014.59.07%402x.png?alt=media&amp;token=cadbc072-7154-4fe2-893f-04c0babffa9e" alt="" width="353"><figcaption></figcaption></figure>

Use a preset (**Default**, **Sidebar**, or **Glass**) from the **Theme library** as-is, or duplicate one to edit its layouts, `styles.css`, and scripts in the code editor. Edits are saved as drafts that you preview and publish. When Pylon updates a preset you've customized, you can review the changes and merge them.

See [Custom themes](/pylon-docs/knowledge-base/styling-and-customization/custom-themes.md) for the theme files, template variables, CSS selectors, scripts, and publishing.

## What visitors see

Built-in themes include:

* A **table of contents** for articles with more than one heading
* Up to five **related articles** at the end of each article
* **Popular articles** on the homepage
* **Tags** on each article, linking to search results for that tag
* A language picker when you support more than one language

When a teammate is signed in to Pylon, articles also show up to three related closed issues, labeled **Internal Only**. Customers never see these.

When a customer is logged into your knowledge base, the chat widget identifies them automatically, so they don't have to enter their name or email.

Custom themes can also link to the previous and next article in a collection.

## SEO

All public articles in your knowledge base are automatically made SEO friendly and indexable by search engines and AI crawlers. See SEO & AI Crawlers.


---

# 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.usepylon.com/pylon-docs/knowledge-base/styling-and-customization.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.