> For the complete documentation index, see [llms.txt](https://gitbook-open-v2-preview.gitbook.workers.dev/url/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-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/documentation/zh/zhan-dian-fang-wen/adaptive-content.md).

# 自适应内容

当用户访问您的站点时，您可能已经了解他们的一些信息——例如他们是谁、订阅了哪个方案，以及可以访问哪些功能。

自适应内容有助于根据阅读者创建定制化的文档体验。

<figure><img src="/files/e25893f59c50a179006aad21eeadb9a943d1a81c" alt="A GitBook screenshot showing adaptive content controls"><figcaption><p>通过自适应内容个性化用户的文档体验</p></figcaption></figure>

{% hint style="info" %}
自适应内容与 [身份验证访问](/url/gitbook.com/docs/documentation/zh/zhan-dian-fang-wen/authenticated-access.md)，不过它们可以协同工作。

虽然身份验证访问可以通过登录来保护您的文档，但自适应内容会根据各种身份验证方式（包括身份验证访问或来自您自己的应用）来定制已发布的内容。
{% endhint %}

### 工作原理

自适应内容有两种工作方式：

1. 将数据从您的应用传递到 GitBook
2. 从身份验证访问传递数据

当用户访问您的站点时，我们将他们随身带来的数据称为“声明”——本质上，这些数据有助于识别用户。这些声明可由您——站点作者——进行控制，并可通过 GitBook 编辑器用于显示或隐藏文档中的不同页面、变体和部分。

前往我们的页面了解 [启用自适应内容](/url/gitbook.com/docs/documentation/zh/zhan-dian-fang-wen/adaptive-content/enabling-adaptive-content.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/documentation/zh/zhan-dian-fang-wen/adaptive-content.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.