> 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-deathscreen/building-the-ui.md).

# Building the UI

Only in the open-source edition. The UI is a Vue 3 app in `web/`. The built files that FiveM loads are in `html/`.

## Requirements

Node.js 20.19+ or 22.12+.

## Build

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

The build writes to `html/` (the folder is emptied first). Restart the resource afterwards.

## Preview in the browser

```bash
npm run dev
```

Open the address that is printed. The page shows a sample screen. Add `?style=center` or `?style=cinematic` to the address to see the other styles.

## Files

| File                       | Purpose                                    |
| -------------------------- | ------------------------------------------ |
| `web/src/App.vue`          | The whole screen: markup, logic and styles |
| `web/src/assets/fonts.css` | The bundled Sora font                      |
| `web/src/assets/fonts/`    | Font files and their license               |

{% hint style="warning" %}
FiveM's browser does not support everything. Do not use `border`, `backdrop-filter` or `color-mix()` in your styles: use `box-shadow` rings and `rgba()` colors 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://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-deathscreen/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.