# Card

<figure><img src="/files/QqubD8ILWLI8DUEUniVj" alt=""><figcaption></figcaption></figure>

## Overview

Cards are a flexible component that helps organize content. They enable to display information in a clear and appealing way, making it easier to read and enhancing the overall appearance of the user interface.

<br>

<figure><img src="/files/2EfFqK5EIWui262lM3nr" alt="" width="375"><figcaption><p>Card with grey background</p></figcaption></figure>

## Guidelines

**Card component must always be used within a panel.** When used outside of a panel, the utilization of the Card component is strictly limited to two defined types: the Clickable Card and the Totalizer Card.

<figure><img src="/files/Bo9PpBWgDbSerICLxyKx" alt=""><figcaption><p>Totalizer and clickable cards are the only cards components to be used outside of a panel</p></figcaption></figure>

The card component provides two background color options: white and grey. For visual distinction among multiple cards within the same panel, opt for a grey background.&#x20;

Beyond this, the design allows for full creative flexibility in terms of padding, elements, and media, with the only requirement being consistency.

### Cards or Datatalist ?&#x20;

[Datalist](/design/components/datalist.md) in its card variation may look a lot like cards. However, there is a slight difference between those two components.

<figure><img src="/files/T3ZLYpD2MwbxeqSP26nW" alt=""><figcaption><p>This is a datalist in a card variation</p></figcaption></figure>

Datalists are best for displaying a collection of similar items, acting like a simpler version of a datatable without all its functionalities. They allow for easy comparison between items since the type of information displayed remains consistent across the list.&#x20;

On the other hand, Cards are more versatile and are not limited to showing repetitive information. Instead, each card can present unique content, making them suitable for a wider range of uses where diverse information needs to be displayed in an engaging way.

<br>


---

# Agent Instructions: 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://design.mirakl.com/design/components/structure/card.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.