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

# Component Variants

Variants are useful when you have one component that has **multiple different possible implementations**. These could be implemented as separate components but often it's easier and more semantic to create them as variants of an existing component.

Let's take a look at the Card component for example. Here are two different ways in which this component will be displayed:

![Default Card component](/files/-M3Jb6gcA5f_KhXI41_P)

![Card wide variant](/files/-M8CN4VLGZDuYPioWuTA)

### Planning for component variants

Looking at the two cards above, we see that they are practically the same card component but with some differences. There are many factors that determine if a component could be used as the base for variants.

* Does the proposed variant have the overall look and feel of the original component?
* Are there common patterns (fields, markup, layout, etc.) that can facilitate a variant vs. a whole new component?
* Does the component behavior and layout lend themselves to new variants without altering markup or sacrificing accessibility or user experience?
* Can I achieve the variants with a CSS modifier class or basic twig logic?

These are questions you should ask yourself before deciding to create component variants. If not properly planned, you could paint yourself in a corner when your components have been over engineered in an effort to accommodate for variants.

#### Let's build the variant next


---

# 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://mariohernandez.gitbook.io/components/card-component/component-variants.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.