> 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/volume-themes/changelog/volume-release-notes/volume-2.0.0.md).

# Volume 2.0.0

Volume 2.0.0 release notes — adds EU languages, info cards, the grid switcher, smart cart panel, and a sticky Add to cart on product pages.

#### Released April 23, 2025

### Added

* **EU languages** — German, French, Spanish, and Italian.
* **Info cards** in the Product slider and Banner slider sections.
* **Grid switcher** — customers can toggle between three product grid layouts on collection pages.
* **Smart cart enhancements** — a new side panel in the Cart drawer displays product recommendations and recently viewed items.
* **Sticky Add to cart** panel on the product page.
* **Before discounts price option** — enable **Theme settings → Cart → Include the compare-at price in the 'Before discounts'** to display original prices based on the compare-at price.
* Refreshed blurred search field, now also available in the mobile header via **Header section → Mobile → Enable search field**.

### Fixed

* Replaced the deprecated secondary heading font with a Shopify-compliant alternative.
* Resolved a screen-jump issue when tapping into the search field on mobile.
* Minor bug fixes and overall performance improvements.


---

# 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/volume-themes/changelog/volume-release-notes/volume-2.0.0.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.