> For the complete documentation index, see [llms.txt](https://docs.remotera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.remotera.ai/contributing.md).

# Maintaining the Fumadocs app

The public documentation site is a self-hosted Fumadocs application. Content lives in `content/docs`, while the site implementation, theme, and search live beside it in `apps/docs`.

## Local development

From the repository root:

```bash
bun install
bun --cwd apps/docs run dev
```

Open `http://localhost:3000/docs`. The root page at `http://localhost:3000` is the documentation landing page.

## Authoring

* Add public user guidance under `content/docs`.
* Use each directory's `meta.json` to control sidebar order.
* Include `title` and `description` frontmatter on every page.
* Use absolute `https://www.remotera.ai` links when moving back to the product.
* Keep engineering notes in the repository's top-level `docs/` directory.
* Do not document private-beta behavior as permanent.

## Production

`bun run build` writes a fully static site to `out/`. The production docs image serves that directory with Nginx behind Traefik at `docs.remotera.ai`; no Fumadocs or Node.js server runs in production.


---

# 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://docs.remotera.ai/contributing.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.