> For the complete documentation index, see [llms.txt](https://support.heyamplify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.heyamplify.com/cart-and-checkout/scenarios/cart.md). # Cart - [Amplify | Power Slide Cart: Learn About Its Features and How It Can Boost Your Store](https://support.heyamplify.com/cart-and-checkout/scenarios/cart/amplify-or-power-slide-cart-learn-about-its-features-and-how-it-can-boost-your-store.md) - [How to Customize the Text in the Power Slide Cart](https://support.heyamplify.com/cart-and-checkout/scenarios/cart/how-to-customize-the-text-in-the-power-slide-cart.md): Learn how to modify the text displayed in the Amplify | Power Slid to align with your store’s branding and preferences. This guide will show you how to edit text elements within the Power Slide Cart. - [How to Insert Custom HTML or Scripts into the Slide Cart](https://support.heyamplify.com/cart-and-checkout/scenarios/cart/how-to-insert-custom-html-or-scripts-into-the-slide-cart.md): Learn how to enhance the functionality of your Slideout Cart by adding custom HTML elements or scripts. This feature allows you to display custom notices, buttons, or integrate third-party scripts. --- # 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://support.heyamplify.com/cart-and-checkout/scenarios/cart.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.