> 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/create-content/guides.md).

# Guides

Explore guides for creating and structuring documentation in GitBook

GitBook’s editor makes it easy to create and customize documentation, whether you’re starting fresh or working in an existing space.

#### Explore

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-pen-ruler">:pen-ruler:</i></h4></td><td><h4>How to use GitBook’s editor</h4></td><td>Create pages, add content blocks, and publish documentation</td><td><a href="/docs/guides/editing-and-publishing-documentation/how-to-use-gitbooks-editor.md">How to use GitBook’s editor</a></td></tr><tr><td><h4><i class="fa-file-import">:file-import:</i></h4></td><td><h4>Import content from a CSV file</h4></td><td>Import documentation from Zendesk or another CSV export</td><td><a href="/docs/guides/editing-and-publishing-documentation/import-zendesk-csv-to-gitbook.md">How to import docs from a CSV</a></td></tr><tr><td><h4><i class="fa-circle-play">:circle-play:</i></h4></td><td><h4>Embed a playable video</h4></td><td>Add video content directly to your documentation</td><td><a href="/docs/guides/editing-and-publishing-documentation/upload-and-embed-a-playable-video-into-your-gitbook-docs.md">How to embed videos in docs</a></td></tr><tr><td><h4><i class="fa-magnifying-glass">:magnifying-glass:</i></h4></td><td><h4>Make batch changes with Git Sync</h4></td><td>Update repeated content across your documentation from a code editor</td><td><a href="/docs/guides/editing-and-publishing-documentation/find-and-replace-or-make-batch-changes-across-your-gitbook-docs-with-git-sync.md">How to find and replace content</a></td></tr></tbody></table>

#### Quick guides

<details>

<summary>How do I structure my documentation?</summary>

Organize pages and groups around the tasks readers need to complete.

This guide covers planning page hierarchy, creating groups, and refining navigation.

<button type="button" class="button secondary" data-action="ask" data-query="How do I structure GitBook documentation around reader tasks? Show me how to plan page hierarchy, create groups, organize pages, and refine navigation. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>

<details>

<summary>How do I reuse content across pages?</summary>

Reusable content keeps shared text consistent across your documentation.

This guide covers creating reusable blocks, inserting them into pages, and updating shared content.

<button type="button" class="button secondary" data-action="ask" data-query="How do I reuse content across GitBook pages? Show me how to create reusable blocks, insert them into pages, and update shared content. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>

<details>

<summary>How do I manage repeated values with variables?</summary>

Variables let you define a value once and reuse it across your content.

This guide covers creating variables, referencing them in pages, and maintaining shared values.

<button type="button" class="button secondary" data-action="ask" data-query="How do I manage repeated values with GitBook variables? Show me how to create variables, reference them in pages, and maintain shared values. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>

<details>

<summary>How do I create a documentation style guide?</summary>

A style guide keeps your documentation consistent across contributors and AI-assisted changes.

This guide covers defining writing rules, adding terminology guidance, and maintaining the guide.

<button type="button" class="button secondary" data-action="ask" data-query="How do I create a GitBook documentation style guide? Show me how to define writing rules, add terminology guidance, and maintain the guide. 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.com/docs/create-content/guides.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.
