> For the complete documentation index, see [llms.txt](https://design.mirakl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://design.mirakl.com/design/components/structure/card.md). # Card Cards are a great way to add some hierarchy and organization to a panel.

## 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.

## 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.

Totalizer and clickable cards are the only cards components to be used outside of a panel

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. 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 ? [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.

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. 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.
--- # 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://design.mirakl.com/design/components/structure/card.md?ask=&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.