> 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/ja-gitbook-documentation/kontentsuwosuru/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://4217681718-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNkEGS7hzeqa35sMXQZ4X%2Fuploads%2FNMfJRm6dUVv7erqeWmAk%2Fcolumns.png?alt=media&amp;token=925af10f-1f4e-40cc-9cd2-cccf213460ff" alt="An image of GitBook icons demonstrating side by side column functionality"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

## Markdownでの表記

<pre class="language-markdown" data-overflow="wrap"><code class="lang-markdown"><strong>## 例
</strong>




### ドキュメントと製品の間にシームレスな体験を作る

ドキュメントを製品体験にそのまま組み込むことも、ユーザーに必要なものをより早く届けるパーソナライズされた体験を提供することもできます。

&#x3C;a href="https://www.gitbook.com/#alpha-waitlist" class="button primary">詳細を見る&#x3C;/a>





&#x3C;figure>&#x3C;img src="../../.gitbook/assets/GitBook vision post.png" alt="GitBook のアイコンが左右のカラム機能を示している画像">&#x3C;figcaption>&#x3C;/figcaption>&#x3C;/figure>




</code></pre>


---

# 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/ja-gitbook-documentation/kontentsuwosuru/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.
