> 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/developer-reference/snippets/change-popup-fonts.md). # Change popup fonts To change the `font-family` of specific parts of the popup, you need to target the appropriate CSS class for that element. {% hint style="warning" %} **Important:** Make sure the font you want to use is already installed in your theme or actively loaded; otherwise, it won’t work. {% endhint %} For example, to change only the font of the popup title, use the following CSS in [Custom code](/settings/custom-code.md): ```css .md-modal__header__title span { font-family: 'Gluten'; } ``` Replace `'Gluten'` with the desired font-family name of your theme. {% hint style="info" %} **Accessibility tip**: if you change the font or font size, use relative units (like rem or %) instead of fixed pixels. Text should scale up to 200% in browser settings without losing content or functionality (WCAG 2.2 – Resize Text, Level AA). {% endhint %} ## Popup element classes
Title.md-modal__header__title spanfont title.png
Text.md-modal__bodyContent pfont text.png
Helper text.md-modal__bodyContent__helperTextfont helper text.png
Labels.md-modal__formContent__selectLabelfont labels.png
Selectors#md-app-embed__modal .md-form__select, #md-app-embed__modal .md-form__select__country__list-link-wrapper spanfont selectors.png
Button.md-btn__primaryfont button.png
{% hint style="info" %} You can also use these CSS classes to apply additional specific styles **that are not available in the app embed settings**. If a style is already provided in the app embed, please use that option instead. {% 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/developer-reference/snippets/change-popup-fonts.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.