> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/appearance-and-localization.md).

# Appearance and localization

Applies to **Classic App Builder**. Screens and recordings in this section show the Classic interface.

Adjust the app's presentation while checking the impact on existing pages and users.

## Choose the scope

* [App theming](/classic-app-builder/appearance-and-localization/app-theming.md) for app-wide styling.
* [Global CSS and JavaScript](/classic-app-builder/appearance-and-localization/global-css-and-js.md) for customizations that may affect multiple pages.
* [Component Designer](/classic-app-builder/component-designer.md) for custom component layout, states, and appearance.
* [Localization](/classic-app-builder/appearance-and-localization/localization.md) for account and end-user language or timezone settings.
* [Application settings](/classic-app-builder/appearance-and-localization/application-settings.md) for related configuration.

## Review a visual change

Check text readability, empty and loading states, long labels, and supported screen sizes. Test interactive states such as hover, focus, and disabled controls where available.

A global CSS change may affect more than the page you are editing. Inspect representative pages after changing shared styling.

For localization, check the intended user's language and timezone separately from the builder's account preferences. Include dates, numbers, and labels in the review.


---

# 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.jetadmin.io/classic-app-builder/appearance-and-localization.md?ask=<question>&goal=<user_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.