> 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/templates/cart-page.md).
# Cart page
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.
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**
* **Empty cart alignment:** When the cart is empty, choose if the content should be aligned to the left, center or right
Empty cart alignment set to "Center"
* **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)
* **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**:
* This is a specialized version of the [mini product](/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](/common-settings.md):
* Color scheme/Color scheme transition
* Padding
* Borders
{% 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/templates/cart-page.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.
