> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/manage-your-site/guides.md).

# Guides

### Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-wand-magic-sparkles">:wand-magic-sparkles:</i></h4></td><td><h4>How to make a great-looking docs site</h4><p>Build a polished visual experience for your documentation.</p></td><td><a href="/spaces/LBGJKQic7BQYBXmVSjy0/pages/Qpj0n0XAUAIoxBGrGX3Z">/spaces/LBGJKQic7BQYBXmVSjy0/pages/Qpj0n0XAUAIoxBGrGX3Z</a></td></tr><tr><td><h4><i class="fa-palette">:palette:</i></h4></td><td><h4>How to customize your site’s theme</h4><p>Set your logo, colors, typography, and navigation style.</p></td><td><a href="/spaces/LBGJKQic7BQYBXmVSjy0/pages/op0lPCqgDi1rNMEz8MMv">/spaces/LBGJKQic7BQYBXmVSjy0/pages/op0lPCqgDi1rNMEz8MMv</a></td></tr><tr><td><h4><i class="fa-table-columns">:table-columns:</i></h4></td><td><h4>How to customize your site’s layout</h4><p>Arrange your documentation’s sections and navigation.</p></td><td><a href="/spaces/LBGJKQic7BQYBXmVSjy0/pages/GA5gazq8sBetctF85CKL">/spaces/LBGJKQic7BQYBXmVSjy0/pages/GA5gazq8sBetctF85CKL</a></td></tr><tr><td><h4><i class="fa-sliders">:sliders:</i></h4></td><td><h4>How to customize your site’s configuration</h4><p>Configure site behavior and your visitors’ experience.</p></td><td><a href="/spaces/LBGJKQic7BQYBXmVSjy0/pages/q6Bxi7QxIvpE6WF1g42B">/spaces/LBGJKQic7BQYBXmVSjy0/pages/q6Bxi7QxIvpE6WF1g42B</a></td></tr><tr><td><h4><i class="fa-layer-group">:layer-group:</i></h4></td><td><h4>Combine multiple existing sites into one using site sections</h4><p>Bring related documentation into one published site.</p></td><td><a href="/spaces/LBGJKQic7BQYBXmVSjy0/pages/MYJwNJuPfwmSWbwZpqwC">/spaces/LBGJKQic7BQYBXmVSjy0/pages/MYJwNJuPfwmSWbwZpqwC</a></td></tr><tr><td><h4><i class="fa-language">:language:</i></h4></td><td><h4>Localize your docs with variants in GitBook</h4><p>Publish localized or versioned documentation with variants.</p></td><td><a href="/spaces/LBGJKQic7BQYBXmVSjy0/pages/yH7Mhwm4GPB0eiDOBS2R">/spaces/LBGJKQic7BQYBXmVSjy0/pages/yH7Mhwm4GPB0eiDOBS2R</a></td></tr></tbody></table>

#### Quick guides

<details>

<summary>Customize your documentation site</summary>

Customize your site’s branding, navigation, and shared settings.

This guide covers colors, typography, layout, and site configuration.

<button type="button" class="button secondary" data-action="ask" data-query="Write a step-by-step guide to customizing a GitBook documentation site. Cover updating branding, choosing a layout, configuring navigation, and reviewing site settings. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>

<details>

<summary>Organize content with sections and variants</summary>

Sections and variants help you structure content for products, audiences, languages, and versions.

This guide covers creating sections, organizing navigation, and configuring variants.

<button type="button" class="button secondary" data-action="ask" data-query="Write a step-by-step guide to organizing a GitBook site with sections and content variants. Cover planning the structure, creating sections, configuring variants, and checking navigation. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>

<details>

<summary>Control site access</summary>

Site audience settings control who can view your published documentation.

This guide covers access options, authenticated access, and testing the visitor experience.

<button type="button" class="button secondary" data-action="ask" data-query="Write a step-by-step guide to controlling access to a GitBook documentation site. Cover choosing an audience, configuring authenticated access when needed, and testing access as a visitor. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>

<details>

<summary>Set up a custom domain</summary>

A custom domain gives your published site a branded address.

This guide covers choosing a subdomain, adding the DNS record, and verifying the setup.

<button type="button" class="button secondary" data-action="ask" data-query="Write a step-by-step guide to setting up a custom domain for a GitBook documentation site. Cover choosing a subdomain, starting setup in GitBook, adding the required DNS record, and verifying the domain. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>

<details>

<summary>Install and configure an integration</summary>

Integrations add analytics, interactive content, and other tools to your documentation.

This guide covers choosing an integration, selecting its scope, and completing configuration.

<button type="button" class="button secondary" data-action="ask" data-query="Write a step-by-step guide to installing and configuring a GitBook integration. Cover choosing an integration, selecting its scope, installing it, and completing any required configuration. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>


---

# 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://gitbook.com/docs/manage-your-site/guides.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.