> 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

## Landing Page

Customize the look and feel of the landing page of your knowledge base with the visual builder in the "Styling" tab of your KB. See the preview change in real-time on the left as you update your configuration.

You can customize:

* Header links
* Header logo
* Footer sections, with categories of links
* Social icons in footer
* Brand color
* Banner image
* Page properties like favicon (inherited from Brand Center) and HTML title

## Custom Domain

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

## Custom Code

Inject custom scripts from the Code page. For example, a script for Google Analytics to collect page views or a tracking pixel for collecting intent data from visitors.

## Custom Themes

Create custom themes from scratch from Pylon from the Knowledge Base > Styling tab.

<figure><img src="/files/VWKozOz4tokXzJFIqKGv" alt="" width="353"><figcaption></figcaption></figure>

Here you can fully customize the code, styling, and scripts in your knowledge base. For more information on what is available with custom themes [see here](https://support.usepylon.com/articles/7918427120-custom-themes?lang=en).

<figure><img src="/files/cmJD4eq5VBzDW4UCbmXz" alt=""><figcaption></figcaption></figure>

## SEO

All public articles in your knowledge base will be automatically made SEO friendly and indexable by search engines and crawlers.&#x20;

You can also provide an OpenGraph image to use in social previews.


---

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