> 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/manage-your-site/customization/layout-and-structure.md).
# 布局与结构
自定义已发布文档的布局和结构
### 页眉
**搜索栏**
在醒目（居中显示在页眉中）和低调（位于右上角）之间更改搜索栏的位置和外观。完全关闭页眉后，搜索栏将改为放置在侧边栏中。
**导航**
向您的网站添加页眉链接。您可以使用页眉链接指向文档中的重要部分，或链接回您的主网站。
您可以选择链接的显示样式——普通链接、主按钮或次按钮。启用后，只需为每个链接添加标题和 URL。我们支持两级页眉导航，这意味着您可以在下拉菜单中显示子链接。
使用 `localizedTitle` 用于本地化页眉链接和按钮标题，以及站点、节和节组标题。
### 公告
开启此选项可在已发布网站的顶部添加公告横幅。您可以添加一条消息，并可选地包含链接和行动号召，它们会显示在横幅中您的消息之后。
您还可以使用与提示块相同的选项更改公告样式——信息、警告、危险和成功。这些样式的颜色由您的语义颜色设置决定。
### 分页
控制在您的节中每个页面底部显示的“上一页”和“下一页”按钮。您也可以为特定页面设置此功能。
### 页脚
**徽标**
在页脚中添加您的徽标或其他图片。
**版权文本**
在页脚中添加版权信息。
**导航**
在页脚中添加链接，并将其组织为多个部分。与页眉类似，为每个链接添加标题和 URL，并为每组链接添加一个部分标题。
使用 `localizedTitle` 用于本地化页脚链接和分组标题，以及站点、节和节组标题。
---
# 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/manage-your-site/customization/layout-and-structure.md?ask=&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.
