> For the complete documentation index, see [llms.txt](https://docs.interaktifotel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interaktifotel.com/zh-cn/bang-zhu-yu-can-kao/gitbook.md).

# 文档管理员的 GitBook 连接指南

本页面是为出版指南的人. 接待人员不需要执行这些步骤.

## 存储库结构

* 存储库根 `gitbook-docs.yaml` 描述网站并将每个语言映射到其文档目录中. 它的文件名没有一个点.
* 土耳其语内容仍然存在 `docs/`. 翻译版在 `docs/languages/` 在他们的语言代码下.
* 每个语言目录都有自己的 `.gitbook.yaml`, `README.md`, `SUMMARY.md` 和 `images/` 文件 ??
* 所有版本的主题文件名称都以英语为本. 截图保留了土耳其接口.

设置如下: [官方的Git同步文件](https://gitbook.com/docs/docs-as-code/git-sync/content-configuration). 编制文件本身并不能连接或发布GitBook网站.

## 连接存储库

1. 检查所有指南文件已提交并将其推向您打算使用的 GitHub 分支.
2. 在 GitBook中打开文件网站的 Git Sync 连接.
3. 选择存储库和分支. 让项目目录空或使用 `./`. 网站配置位于存储库根,并将每个语言映射到自己的文件 ??.
4. 为初步同步,将现有的GitHub内容导入GitBook. 如果您已经在 GitBook 中有内容,请查看所选的同步方向.
5. 预览语言版本,页面顺序,图像和内部链接.
6. 在您的帐户中设置发布地址和访问设置,然后随时发布.

## 缺失配置错误

如果GitBook报告说 `gitbook-docs.yaml` 如果该分支不存在,请检查是否有正确命名的文件在选择的远程分支的根位. 一个地方文件不够. 任何一个 `.gitbook-docs.yaml` 也没有 `.gitbook.yaml` 取代了网站配置. 按下文件后,再用同一个分支.

不设置项目目录为 `docs` 对于这个配置. 每个映射的语言目录使用 `root: ./` 在本文中 `.gitbook.yaml` 文件. 在同步后保持现有空间密钥稳定;使用标题字段重新命名.

## 维护翻译

当一个操作或屏幕发生变化时,请在每个语言版本更新匹配页面. 列出每一个新页面, `SUMMARY.md`. 保持图像链接相对和映射语言文件 ?? 中,以便GitHub和GitBook可以解决它们.

更新截图和说明. 在 Git Sync 启用时,将 README 编辑存储库中保存. 不要记录不可用功能或非功能实时演示地址.


---

# 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://docs.interaktifotel.com/zh-cn/bang-zhu-yu-can-kao/gitbook.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.