> For the complete documentation index, see [llms.txt](https://help.checkoutbuilder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.checkoutbuilder.com/advanced-branding-editor.md). # Advanced branding editor Ready to take your Checkout's branding to the next level? Your in good hands with our one-of-a-kind branding editor with preview. ## Exciting updates on the way. Full documentation coming soon Looking to get started now? No worries. We'll help you get setup within 24 hours, [contact us](/overview/support.md). *** ### 📬 Support Need help? Our support team is here—just reach out below. 👉 Visit the [Support](https://help.checkoutbuilder.com/support) page\ 📧 Email us at \ 💬 Or use the chat icon in the bottom right corner of the app dashboard. We’re here to help! --- # 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://help.checkoutbuilder.com/advanced-branding-editor.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.