> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/styling/customizing-appearance/comparison.md).
# Comparison cards
Configuring your comparison cards
In the Theme menu, there are three options for styling comparison cards: Default, Highlighted, and Selected.
**Default**: this is the default state of the card, and inherits styling from the default theme. No additional configuration is required except adding a comparison card to the step, but additional/differentiating styling can be added if desired.
**Highlighted**: if an option has been designated as "highlighted" in the [question settings](/adding-questions-and-content/question-reference/comparison.md#adding-choices), the styling for the highlighted card can be set here.
**Selected**: styling for when a card has been selected by the user.
Each of the above three configurations can be further styled on a per-UI state basis: default and hover.
The **horizontal overflow behavior** selector controls how the cards fill the space on the step, and has two settings, **wrap** and **scroll**.
* Wrap**:** if the container holding the cards exceeds the width allotted for the container of the step, the cards will begin to stack vertically.
* Scroll: if the cards exceed the width allotted, the a horizontal scroll will become available.
Related pages: [Content Types: Comparison](/adding-questions-and-content/question-reference/comparison.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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.formsort.com/styling/customizing-appearance/comparison.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.
