> 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/chuang-jian-nei-rong/blocks/columns.md).

# 列

添加列以在文档中创建不同布局。

列是为你的文档创建不同布局的好方法。你可以在一列中添加许多不同类型的区块，并调整每一侧的宽度，使其适配你所需的设计。

{% columns %}
{% column width="50%" %}
**在文档与产品之间打造无缝体验**

将你的文档直接集成到产品体验中，或者为用户提供个性化体验，让他们更快获得所需内容。

<a href="https://www.gitbook.com/#alpha-waitlist" class="button primary">了解更多</a>
{% endcolumn %}

{% column %}

<figure><img src="https://2111890564-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNkEGS7hzeqa35sMXQZ4X%2Fuploads%2Fgit-blob-1e2507fae2a187e47b5ca9e2249216ffddc76f58%2F25_12_10_columns.png?alt=media" alt="An image of GitBook icons demonstrating side by side column functionality"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

## Markdown 表示

{% code overflow="wrap" %}

```markdown
## 示例

{% columns %}
{% column width="50%" %}
### 在文档与产品之间打造无缝体验

将你的文档直接集成到产品体验中，或者为用户提供个性化体验，让他们更快获得所需内容。

<a href="https://www.gitbook.com/#alpha-waitlist" class="button primary">了解更多</a>
{% endcolumn %}

{% column %}
<figure><img src="../../.gitbook/assets/GitBook vision post.png" alt="一张展示 GitBook 图标并演示并排列功能的图片"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}
```

{% endcode %}


---

# 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/chuang-jian-nei-rong/blocks/columns.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.
