> 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-tw/shuo-ming-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-tw/shuo-ming-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.