> 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/design-and-structure/core-concept/jet-ui/layouts-and-branding/custom-scripts-and-styles.md).

# Custom Scripts & Styles

In this section you will learn about Custom Scripts and Styles

**Scripts & Styles** allow you to set global JavaScript and CSS. **Global JavaScript** might come in handy for use cases such as setting up a chat functionality in your app. **Global CSS** will allow you to customize the appearance of different UI components, but unlike page-specific CSS, the changes will apply to all the UI components of the same type. It might be helpful if you want to change the shape of all buttons in your app at once.

You can access them in this section of the App Settings menu.

<figure><img src="https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FJhybZ832Os6fvCQgVMic%2Fimage.png?alt=media&amp;token=bb376d10-c003-447a-b81d-3d66d910078d" alt=""><figcaption></figcaption></figure>

Learn more about Global JavaScript and CSS in [this article](/classic-app-builder/appearance-and-localization/global-css-and-js.md).&#x20;


---

# 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/design-and-structure/core-concept/jet-ui/layouts-and-branding/custom-scripts-and-styles.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.