> 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/settings/custom-code.md).
# Custom code
How do I apply CSS code to personalize the geolocation popup?
Many brands enhance their geolocation popups by adding identifying elements like their logo.
If you have a paid Orbe plan, you can customize the Geolocation Modal CSS through the "Settings" menu. Our editor allows you to apply CSS for customizing the modal.
{% hint style="info" %}
Consider that the Custom CSS editor won't appear in your settings until you upgrade your plan.
{% endhint %}
## Do you not know CSS?
Our Help Center has a collection of CSS Snippets available exclusively for users of our paid plan. These snippets make it easy for you to customize your popup's appearance without any coding knowledge. With just a few clicks, you can effortlessly enhance your storefront and create a unique brand style.
By simply copying and pasting these pre-written snippets into the 'Custom CSS' section of our app's Advanced Settings, you can instantly transform the look and feel of your popup. It's that simple!
To explore and leverage these powerful CSS Snippets, visit our dedicated page in the Help Center. Unleash your creativity and make your popup truly stand out!
---
# 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/settings/custom-code.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.
