# Page Not Found

The URL `appendix/unpinned` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [5.1 Channel](https://rainbowmango.gitbook.io/go/di-wu-zhang-bing-fa-kong-zhi/5.1-channel.md)
- [7.4 扩展阅读](https://rainbowmango.gitbook.io/go/di-qi-zhang-ce-shi/7.4-kuo-zhan-yue-du.md)
- [2 循环变量绑定](https://rainbowmango.gitbook.io/go/fu-lu-yi-bian-cheng-xian-jing/2-xun-huan-bian-liang-bang-ding.md)
- [9.2 Ticker](https://rainbowmango.gitbook.io/go/di-jiu-zhang-ding-shi-qi/9.2-ticker.md)
- [12.2 vendor](https://rainbowmango.gitbook.io/go/di-shi-er-zhang-go-yi-lai-guan-li/12.2-vendor.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://rainbowmango.gitbook.io/go/di-wu-zhang-bing-fa-kong-zhi/5.1-channel.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 `build a script that syncs our docs to a CMS` 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.

### Option 2 — Browse the documentation index

Full index: https://rainbowmango.gitbook.io/go/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://rainbowmango.gitbook.io/go/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/go/di-wu-zhang-bing-fa-kong-zhi/5.1-channel.md`).

You may also use `Accept: text/markdown` header for content negotiation.