> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/avante-themes/faq/theme-setup/whats-the-difference-between-adelle-bloop-ariste-vente-and-avante.md).

# What's the difference between Adelle, Bloop, Ariste, Vente, and Avante?

Adelle, Bloop, Ariste, Vente, and Avante are style presets within one theme, not separate products. Switch between them in Theme settings → Theme style.

Adelle, Bloop, Ariste, Vente, and Avante are built-in theme styles inside the Avante theme.

They are not separate themes. You do not need to buy them individually.

Switching styles changes the overall visual look of your store, including colors, fonts, and other design settings.

### Switch between theme styles

1. Open **Theme Editor**.
2. Click **Theme settings** on the left.
3. Open **Theme style**.
4. Select the preset you want to use.

<figure><img src="https://795663372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6DraMvJNYYlFJqlho1aV%2Fuploads%2FbNlYXBxOSlqCZFuyozcf%2FScreenshot%202026-06-08%20at%2017.17.49.png?alt=media&amp;token=8723fb19-e5e1-4b41-a1e7-2a0b39f6132b" alt=""><figcaption></figcaption></figure>

{% hint style="warning" icon="triangle-exclamation" %}
Switching presets updates visual settings only.

Shopify does not automatically recreate the full demo content structure.

If you want the exact layout from one of the demos, install that preset fresh from the Shopify Theme Store.
{% endhint %}

{% hint style="info" %}
**Vortex is no longer part of the theme.** It was retired in Avante 16.0.0 and does not appear in the Theme style list. Stores that were already built on Vortex keep their settings — nothing is reset by updating — but the preset cannot be selected again.
{% endhint %}


---

# 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://staylime.com/docs/avante-themes/faq/theme-setup/whats-the-difference-between-adelle-bloop-ariste-vente-and-avante.md?ask=<question>&goal=<user_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.
