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

# Knowledge Base

- [Overview](https://docs.usepylon.com/pylon-docs/knowledge-base/overview.md): A dedicated place to host your support content, including question-and-answer style articles, internal runbooks, and more -- all supercharged with AI and tightly integrated with the Pylon platform.
- [Articles & Collections](https://docs.usepylon.com/pylon-docs/knowledge-base/articles-and-collections.md): How articles and collections within the knowledge base function
- [Editor](https://docs.usepylon.com/pylon-docs/knowledge-base/articles-and-collections/editor.md): How to use Pylon's WYSIWG editor to write knowledge base content
- [Copilot](https://docs.usepylon.com/pylon-docs/knowledge-base/articles-and-collections/copilot.md): Use AI Assistant features to help streamline your knowledge curation.
- [Templates](https://docs.usepylon.com/pylon-docs/knowledge-base/articles-and-collections/templates.md): Create templates for common article formats
- [Collaboration](https://docs.usepylon.com/pylon-docs/knowledge-base/articles-and-collections/collaboration.md): Work on knowledge base content together with your team
- [Article Review](https://docs.usepylon.com/pylon-docs/knowledge-base/articles-and-collections/article-review.md): Request reviews on articles before publishing to ensure content quality and accuracy.
- [Synced Blocks](https://docs.usepylon.com/pylon-docs/knowledge-base/articles-and-collections/synced-blocks.md): Synced blocks let you reuse the same content across multiple knowledge base articles.
- [Translations](https://docs.usepylon.com/pylon-docs/knowledge-base/translations.md): Translate knowledge base articles, collections, and headers into your supported languages.
- [Missing Content](https://docs.usepylon.com/pylon-docs/knowledge-base/missing-content.md): Discover gaps in your documentation
- [Analytics](https://docs.usepylon.com/pylon-docs/knowledge-base/analytics.md): See how your knowledge base is used, what customers search for, and how helpful articles are.
- [Styling & Customization](https://docs.usepylon.com/pylon-docs/knowledge-base/styling-and-customization.md): Customize the look and feel of your knowledge base
- [Custom themes](https://docs.usepylon.com/pylon-docs/knowledge-base/styling-and-customization/custom-themes.md): Build your own knowledge base layouts with templates, CSS, and scripts, then preview and publish them.
- [Custom Authentication](https://docs.usepylon.com/pylon-docs/knowledge-base/custom-authentication.md): Add unified sign-in between the customer portal and your product dashboard
- [Search](https://docs.usepylon.com/pylon-docs/knowledge-base/search.md): Allow your team and users to search for knowledge
- [Redirects](https://docs.usepylon.com/pylon-docs/knowledge-base/redirects.md): Keep old links working when you move to Pylon or reorganize your knowledge base.
- [SEO & AI Crawlers](https://docs.usepylon.com/pylon-docs/knowledge-base/seo-and-ai-crawlers.md): How Pylon makes your public knowledge base discoverable by search engines and AI tools.


---

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