> For the complete documentation index, see [llms.txt](https://help.orbe.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.orbe.app/geolocation-popup/getting-started/customize/style.md).
# Style
Match the look and feel of the popup with your storefront design. No coding required.
From buttons to colors, these settings let you control the visual experience and make the popup feel fully integrated with your brand.
## **Button and selector style**
Choose between **rounded** or **squared** corners to better match your store’s design aesthetic.
## **Selector type**
Decide how visible you want the selector to be: pick between **outlined**, **underlined**, or a minimal look with **no lines**.
## **Button alignment**
Position your action button wherever it works best: **left**, **center**, **right**, or stretch it to be **full-width**.
## **Font size**
Fine-tune the popup’s appearance by setting the **title and body text sizes** in pixels. Simple and precise.
## **Blurred background**
Hide product prices and content until the customer selects their shopping experience. This feature is ideal if your store has region-specific pricing, as it prevents price confusion and keeps your presentation consistent across markets.
A smart way to keep sensitive info hidden until customers land in the right version of your store.
## **Colors**
Make the popup feel native to your storefront by **customizing its colors** to match your brand identity.
{% hint style="info" %}
**Accessibility tip**: when setting modal colors, especially the button, make sure it’s easy to see for everyone. The button color should contrast at least **3:1** with the modal background (WCAG 2.2 – 1.4.11 Non-text Contrast, Level AA), and the button text should contrast at least **4.5:1** with the button color (WCAG 2.2 – 1.4.3 Contrast (Minimum), Level AA).
{% 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://help.orbe.app/geolocation-popup/getting-started/customize/style.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.
