> For the complete documentation index, see [llms.txt](https://docs.zingy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingy.ai/app-editor/page-editor/built-in-elements/card-group.md).

# Card Group

<div align="left"><figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2FwpX6Db6oqr8wTooafBFc%2Fimage.png?alt=media&amp;token=74523d11-433e-4354-94e1-b93057655398" alt="" width="67"><figcaption><p>Card Group</p></figcaption></figure></div>

The **`Card Group`** is a pre-built responsive element that is designed to show a group of related [Card](/app-editor/page-editor/built-in-elements/card.md) elements.

The element is composed of 1 [Layout Container](/app-editor/page-editor/built-in-elements/layout-container.md) element with:

* 1 [Layout Row](/app-editor/page-editor/built-in-elements/layout-row.md) configured to show a 3 column layout for larger screens and a single column layout for smaller screens (via its [Column Layout Format](/app-editor/page-editor/built-in-elements/layout-row.md#column-layout-format) setting).
* 3 [Layout Column](/app-editor/page-editor/built-in-elements/layout-column.md) elements inside the Layout Row.

To add cards into the group, simple drag and drop the [Card Style1](/app-editor/page-editor/built-in-elements/card-style1.md), [Card Style2](/app-editor/page-editor/built-in-elements/card-style2.md) and [Card Style2](/app-editor/page-editor/built-in-elements/card-style3.md) elements into the Layout Column elements.&#x20;

<figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2F4DS1WzguvnmeDmFXLXDU%2Fimage.png?alt=media&amp;token=71fb6de6-81bb-4709-b7c8-5f1a4a96c75e" alt=""><figcaption><p>Example Card Group with <a href="/app-editor/page-editor/built-in-elements/card-style1.md">Card Style1</a>, <a href="/app-editor/page-editor/built-in-elements/card-style2.md">Card Style2</a> and <a href="/app-editor/page-editor/built-in-elements/card-style3.md">Card Style3</a> elements.</p></figcaption></figure>

If you need more cards:

* [Clone](/app-editor/page-editor/working-with-page-elements.md#clone-the-selected-element) one of the Layout Columns
* Add the additional card into the cloned column

You can customize the card group's layout by modifying the [Column Layout Format](/app-editor/page-editor/built-in-elements/layout-row.md#column-layout-format) setting for the layout row.


---

# 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.zingy.ai/app-editor/page-editor/built-in-elements/card-group.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.