> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-admin/building-the-ui.md).

# Building the UI

The open source edition ships the Vue 3 source of the interface in `web/`. The compiled files in `web/dist` are what the game loads, so rebuild after every change.

```bash
cd web
npm install
npm run build
```

Restart the resource after the build: `restart daddy-admin`.

## Preview in a browser

```bash
cd web
npm run dev
```

Open the address Vite prints. The browser preview runs on sample data and starts in English; add `?lang=tr` (or `de`, `fr`, `es`, `pt-br`, `ar`, `ru`) to the address for another language. The bar at the top switches between the panel, the quick menu, the compact bar and the ticket form. It only shows in the browser, not in game.

## Notes for FiveM

* The game's browser is an older Chromium. Colors written as `oklch()` are converted to `rgb()` during the build (`web/src/utils/oklch.ts`), keep that plugin in `vite.config.ts`.
* Fonts (Geist Sans and Geist Mono) are bundled, the interface makes no requests to the internet.
* The map tiles in `web/public/map` are copied into `web/dist/map` by the build.


---

# 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://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-admin/building-the-ui.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.