> 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/documentation/zh/chuang-jian-nei-rong/content-structure.md).

# 内容结构

了解站点、分区、组和页面如何组织你的 GitBook 内容。

GitBook 中的内容围绕文档站点进行组织。你的组织包含多个站点，每个站点由 **分区** 组成——你编写和编辑的页面都位于某个分区中。

相关分区可以归入 **分组** ，以构建站点的导航结构。你在编辑时看到的结构，与访客在已发布的站点上看到的结构相同。

<table data-card-size="large" 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-globe">:globe:</i></h4></td><td><h4>站点</h4></td><td>创建一个站点，用于发布和整理你的文档。</td><td><a href="https://gitbook.com/docs/documentation/zh/publish/publish-a-docs-site.md">发布文档站点</a></td></tr><tr><td><h4><i class="fa-layer-group">:layer-group:</i></h4></td><td><h4>分区</h4></td><td>创建部分，以组织站点内的内容。</td><td><a href="https://gitbook.com/docs/documentation/zh/chuang-jian-nei-rong/content-structure/space.md">分区</a></td></tr><tr><td><h4><i class="fa-folder">:folder:</i></h4></td><td><h4>组</h4></td><td>创建组，以组织站点中的相关部分。</td><td><a href="https://gitbook.com/docs/documentation/zh/chuang-jian-nei-rong/content-structure/collection.md">组</a></td></tr><tr><td><h4><i class="fa-file-lines">:file-lines:</i></h4></td><td><h4>页面</h4></td><td>创建页面，以拆分并编辑文档中的内容。</td><td><a href="https://gitbook.com/docs/documentation/zh/chuang-jian-nei-rong/content-structure/page.md">页面</a></td></tr></tbody></table>


---

# 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/documentation/zh/chuang-jian-nei-rong/content-structure.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.
