> For the complete documentation index, see [llms.txt](https://test-915.gitbook.io/staticdevelopment/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://test-915.gitbook.io/staticdevelopment/introduction.md).

# INTRODUCTION 

## Static Development Docs

Welcome to the official documentation for **Static Development**.

These docs cover everything you need to install, configure, and maintain our FiveM resources — including setup steps, config options, troubleshooting, and updates.

### What we focus on

* **Standalone scripts** (no framework required)
* **Clean, modern UI** where it matters
* **Performance-first** design (lightweight + optimized)
* **Clear setup** with straightforward configs

### Where to start

* **Quickstart / Installation** → first-time setup + updating resources
* **Scripts** → full guides for each product (features, configs, commands)
* **Troubleshooting** → common issues and fixes
* **Changelog** → what changed in each update

### Need help?

If you get stuck, reach out in our Discord support channels and include:

* Script name + version
* Any console/F8 errors
* Your framework (if any) + server build
* A short clip or screenshot if it’s UI-related

Thanks for using Static Development.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://test-915.gitbook.io/staticdevelopment/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.