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

# Building the UI

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

```bash
cd web/source
corepack enable
pnpm install
pnpm build
```

Restart the resource after the build: `restart daddy_college`.

## Preview in a browser

```bash
cd web/source
pnpm dev
```

Open `http://localhost:3106/?panel`. The dev panel opens every screen with sample data and shows or hides the HUD cards (notices, the student card, the hall pass, the off-campus warning, notifications, progress slips and key prompts). It only exists in the browser preview, never in game.

## Notes for FiveM

* The game's browser is Chromium 103. The CSS goes through `postcss-fivem.js` (in `apps/college`): borders become inset rings, `inset` is written out as top, right, bottom and left, `backdrop-filter` is removed, and `color-mix()` fails the build. Keep it in `postcss.config.js`, and keep `cssTarget: 'chrome86'` in `vite.config.ts` so the minifier does not fold `inset` back.
* Fonts (Geist, Geist Mono, Kalam and Sora) are bundled, the interface makes no requests to the internet.
* `waypoint.html` is the sign drawn over marked places in the world; it is built as a second page next to `index.html`.


---

# 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-college/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.