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

# 全部内容

在一个界面中浏览、搜索并管理你所有站点中的内容，以及尚未属于站点的内容

在 GitBook 中，内容位于 [分区](https://gitbook.com/docs/documentation/zh/manage-your-site/site-structure/site-sections.md) 中，这些分区隶属于文档站点。 **所有内容** 页面让你可以在一个位置查看组织中的所有内容：包括每个站点中的内容，以及尚未归属于任何站点的内容。

### 打开所有内容

在组织的 **主页**中，点击侧边栏里的 **内容** 。

### 浏览、筛选和搜索

每一行显示内容名称以及最后更新时间。点击某一行即可打开它。

若要缩小列表范围，请点击 **所有站点** 筛选器并选择一个站点。若要按名称查找内容，请使用 **搜索内容** 字段。

### 创建内容

点击 **创建内容** 即可从此页面开始创建内容。

最好让内容隶属于某个父级站点。尽可能在站点内创建内容，这样结构、权限和发布管理都能集中在一处。请参阅 [站点结构](https://gitbook.com/docs/documentation/zh/manage-your-site/site-structure.md) ，了解分区如何构成站点。

### 不属于某个站点的内容

如果你的组织在我们重构导航之前使用过 GitBook，那么与站点关联的空间已变为该站点的版块。没有任何内容被删除或取消发布。

尚未关联到站点的内容仍会显示在 **所有内容**中，你可以继续在此处编辑并与他人协作。

若要发布这些内容，请将其作为分区添加到某个站点。详情请参阅 [站点结构](https://gitbook.com/docs/documentation/zh/manage-your-site/site-structure.md).


---

# 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/all-content.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.
