> For the complete documentation index, see [llms.txt](https://docs.santacruzsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.santacruzsoftware.com/gemini-home/readme.md). # Welcome Welcome to BrandingUI, your web-based platform for template customization and corporate branding consistency. BrandingUI enables organizations to customize marketing and business templates while maintaining strict brand integrity. These docs cover everything you need as an administrator orchestrating workflows. *** ## Where to start * [**Getting started**](broken://pages/bxyJerDvdcKnTcawEYQu): Jump right in with administrative setup steps. * [**Core concepts**](/gemini-home/core-concepts/core-concepts.md): Understand how assets and jobs work together. * [**Guides**](/gemini-home/guides/guides.md): Step-by-step asset-management and site-configuration workflows. * [**Reference**](/gemini-home/reference/reference.md): Account differences, completion methods, troubleshooting, and terminology. ## Core Features * **Visual Template Customization**: Edit Categories, Keywords, and Options without changing core brand elements. * **Multi-Level Approval Routing**: Send work to the right reviewers automatically. * **Variable Data Printing (VDP)**: Create personalized print assets from spreadsheet data, and bulk merge into designed templates with instant preview. * **Digital Package Editing**: Create and customize digital packages across multiple artboards and dimensions simultaneously. --- # 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.santacruzsoftware.com/gemini-home/readme.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.