> For the complete documentation index, see [llms.txt](https://ebay.gitbook.io/mindpatterns/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ebay.gitbook.io/mindpatterns/structure/item-card.md).

# Item Card

An item card is a display element that is not itself interactive, but houses elements, such as an image wrapped by an anchor, an add to favorites button, item title that is also wrapped in an anchor, etc.

<figure><img src="/files/3bA4Y5hWkcuPrlUSmQOZ" alt=""><figcaption><p>Typical Item Card</p></figcaption></figure>

## Interaction/Keyboard Design

The interaction inside an item card should be simple keyboard `TAB` navigation of interactive elements with the `ENTER` key activating the element in focus.

## Grouped Item Cards

Item cards typically display in groups.&#x20;

<figure><img src="/files/JotHHtFKFPlhnXgKKjfH" alt=""><figcaption><p>Grouped </p></figcaption></figure>

Grouped item cards use and inherit the `a11y` setup of Layout Grid. For more information about using the grouped item cards, please see the [Layout Grid pattern](/mindpatterns/structure/layout-grid.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, and the optional `goal` query parameter:

```
GET https://ebay.gitbook.io/mindpatterns/structure/item-card.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.