> For the complete documentation index, see [llms.txt](https://docs.ultramarinastudios.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ultramarinastudios.com/sections/cart-drawer.md).

# Cart drawer

In **Theme Settings > Cart**, you can choose whether to have a **cart drawer** or a use a **page** instead, as well as a number of other global cart settings. Find out more about global cart settings on our designated [cart settings](https://docs.ultramarinastudios.com/theme-settings/cart) page.

This article will take you through the settings specific to the **drawer**, although you'll notice it shares a lot of commonalities with page settings.

### Settings

* **Heading size**
* **Layout on desktop:** Choose between **horizontal** and **vertical**<br>

<div><figure><img src="https://3146423938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZQuVfmt0J7tzTvfBqG6C%2Fuploads%2FuHwONr8ULpQarqbKgDiC%2Fcart-drawer-primavera.webp?alt=media&amp;token=bd7572d9-541f-43db-ab32-20f3f9bc9d5f" alt="A cart layout where items and cart controls are stacked vertically, occupying the right side of the screen"><figcaption><p>Vertical layout on the Primavera preset</p></figcaption></figure> <figure><img src="https://3146423938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZQuVfmt0J7tzTvfBqG6C%2Fuploads%2FHWWsqpFDh5IhbQM03h5G%2Fcart-drawer-savoir.webp?alt=media&amp;token=099e9bf0-9431-4770-8d85-dc97fef7f06c" alt="A cart layout where items and cart controls are stacked horizontally, occupying the top half of the screen."><figcaption><p>Horizontal layout on the Savoir preset</p></figcaption></figure></div>

* **Show dynamic checkout:** See Shopify's documentation about [accelerated checkout](https://shopify.dev/docs/storefronts/themes/pricing-payments/accelerated-checkout#implementing-accelerated-checkout-buttons-in-your-theme)
* **Show View cart button**: When enabled, a "View cart" button appears under the main checkout buttons and navigates users to the [cart page](https://docs.ultramarinastudios.com/templates/cart-page.md)
* **Products:** This affects the cart items as well as any **Upsell product blocks** you add.
  * **Image width**: Product image width from 70 to 200. Be mindful of checking how this affects the cart on smaller screens.
  * **Product title font**
  * **Price font**

### Blocks

**Upsell product**:&#x20;

* This is a specialized version of the [mini product](https://docs.ultramarinastudios.com/blocks/mini-product.md) which inherits the **product title font**, **price font** and **image width** specified for the cart drawer (see above)
* It also comes with additional **text** and **text font style** settings to provide optional context about the upsell

{% hint style="info" %}
Can't find the setting you're looking for?  The following settings are explained in detail in [common settings](https://docs.ultramarinastudios.com/common-settings.md):

* Color scheme
  {% 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://docs.ultramarinastudios.com/sections/cart-drawer.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.
