> 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/global-sections/cart-drawer.md).

# Cart drawer

The cart drawer slides over the page. The terms checkbox is one Theme settings control, and it also shows on the cart page.

The Cart drawer slides over the page. It is added in the Overlay group.

{% hint style="info" %}
**Theme settings → Cart → Enable cart drawer** turns the drawer on. **Action after adding to cart** chooses what opens after a product is added: **Display cart drawer**, **Display success popup with suggestions**, or **Disabled**.
{% endhint %}

The cart icon is covered in [The cart icon opens the cart page](https://staylime.com/docs/volume-themes/faq/cart-and-checkout/the-cart-icon-opens-the-cart-page.md).

### Terms checkbox

The checkbox before checkout is **Theme settings → Cart → Checkbox**. It is not a setting on the Cart drawer section. The same checkbox shows on the cart page and in the drawer.

* **Enable checkbox** is off until you turn it on.
* **Text** is the label. It starts as "I have read and agreed to the Terms and Conditions." Clear **Text** and the checkbox disappears, even if **Enable checkbox** is on.
* **Make it required** stops the **Checkout** button until the box is checked. **View cart** still opens the cart page.

### Related

* [Preorder notice](https://staylime.com/docs/volume-themes/theme-settings/preorder-notice.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 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/global-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.
