> For the complete documentation index, see [llms.txt](https://docs.optis.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optis.me/swatch/styling/styling-overview.md).

# Styling overview

The **Styling** page lets you control how each display type looks on your storefront, with a live preview and no coding required.

## How styling works

* Styling is set **per display type**: Swatch, Swatch card, Pill swatch, Button, and Dropdown. Each type has its own settings.
* Each type is styled separately for the **Product page** and the **Collection page** (two tabs), so you can use a larger swatch on the product page and a compact one on collection listings.
* A **live preview** shows your changes instantly. Click **Save** to apply them to your store.

{% hint style="info" %}
Styling applies **globally** to every product using that display type. To change how a single option is displayed (for example, switch from Swatch to Button), use **Configure Variants** instead.
{% endhint %}

## Where to find it

{% stepper %}
{% step %}

### Open Styling

In the app, go to the **Styling** page.
{% endstep %}

{% step %}

### Pick a display type

Choose the display type you want to customize: **Swatch / Swatch card / Pill swatch / Button / Dropdown**.
{% endstep %}

{% step %}

### Choose the page

Switch between the **Product Page** and **Collection Page** tabs to style each surface independently.
{% endstep %}

{% step %}

### Adjust and save

Change the settings, watch the live preview, then click **Save**.
{% endstep %}
{% endstepper %}

## Good to know

* **Swatch card** and **Pill swatch** are styled for the **product page only** (they are not available on collection pages).
* For the full list of every setting and what it does, see [Styling settings reference](/swatch/styling/styling-settings-reference.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://docs.optis.me/swatch/styling/styling-overview.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.