# Docs best practices

- [How to create branded documentation](https://gitbook.com/docs/guides/docs-best-practices/how-to-create-branded-documentation.md): Make your docs match your brand with a custom domain, logo, color scheme and more
- [How to structure technical documentation: information architecture best practices](https://gitbook.com/docs/guides/docs-best-practices/documentation-structure-tips.md): Learn information architecture best practices to structure technical documentation — including  API docs, product docs, guides, FAQs, and changelogs — so users can find answers fast
- [Make your documentation process more collaborative with change requests](https://gitbook.com/docs/guides/docs-best-practices/make-your-documentation-process-more-collaborative-with-change-requests.md): Change requests in GitBook make it easier for your whole team contribute to the documentation process — whether they’re editing pages, reviewing changes, or just leaving feedback
- [How to encourage contributions to your open source documentation](https://gitbook.com/docs/guides/docs-best-practices/how-to-encourage-contributions-to-your-open-source-documentation.md): 7 things you can do to make it easier for contributors to write docs for your OSS project


---

# Agent Instructions: 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:

```
GET https://gitbook.com/docs/guides/docs-best-practices.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.