> 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 中的内容围绕你的文档站点进行组织。你的组织包含站点，而每个站点由 **部分** —— 你编写和编辑的页面位于一个章节中。
相关章节可以组织到 **组** 中，以构建你网站的导航。你在编辑时看到的结构，与访客在已发布站点上看到的结构相同。
| | | |
|---|
:globe: | 站点 | 创建一个站点来发布和组织你的文档。 | 站点工作区 |
:layer-group: | 部分 | 创建章节来组织你站点中的内容。 | 分区 |
:folder: | 组 | 创建组来组织你站点中的相关章节。 | 组 |
:file-lines: | 页面 | 创建页面来拆分并编辑你文档中的内容。 | 页面 |
---
# 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/documentation/zh/chuang-jian-nei-rong/content-structure.md?ask=&goal=
```
`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.