# Docs site limits and errors

## Limits

- **Nuxt only.** `@vite-hub/docs` is a Nuxt module. A Vite app without Nuxt cannot use it.
- **One theme.** `vercel` is the only theme. Change it with `app.config.ts` and CSS variables, or replace components. See [Theme](https://vitehub.dev/docs/docs-site/configure#theme).
- **One content folder.** The module reads one folder, `dir`. Sections are the folders under `base`. A page cannot be in two sections.
- **Pages are read at build time.** The manifest, the agent copies, and the routes come from the files at build time. A production site does not see a file that you add after the build. In development, a body change shows on the next page load, and a new page, title, or order restarts the app.
- **No page at `/docs` by default.** Add `content/docs/index.md`, or `/docs` is not found. The Docs links then open the first section.
- **Search is in the browser.** The dialog loads the whole index the first time it opens. Each `h2` and `h3` is one entry. Page titles rank first, then headings, then text.
- **The docs assistant runs on Node.js only**, and on the ChatGPT plan only in the development server. See the [assistant limits](https://vitehub.dev/docs/docs-site/assistant#limits) for plan use, shell access, and the rate limit.

## Errors

### DocsContentError

The frontmatter of a page, or a `.navigation.yml` file, does not match the schema. The build stops on the first invalid file. The message names the file and each wrong field:

```txt [output/docs-content-error.txt]
Invalid docs frontmatter in content/docs/guide/install.md: layout: Invalid type: Expected ("article" | "tutorial" | "landing") but received "wide"
```

**Why:** a required field is missing, such as `title`, or a field has a wrong value or type.

**Fix:** correct the field that the message names. The [frontmatter reference](https://vitehub.dev/docs/docs-site/server-api#frontmatter) lists every field and its values. In development, the terminal shows the error and the site keeps the last valid pages until you fix the file.

### DocsAssistantSetupError

The build shows it as `[@vite-hub/docs]` followed by the cause and the fix. It has two causes.

**Why:** `assistant` is on, and the app has no `vite-hub/nuxt` module with `agent: true`.

**Fix:** add `['vite-hub/nuxt', { agent: true, connections: true, database: true }]` to `modules`. Or set `assistant: false`. See [Turn it on](https://vitehub.dev/docs/docs-site/assistant#turn-it-on).

**Why:** `assistant` is on, and a production build uses a Nitro preset that is not Node.js, such as `cloudflare-module`. Codex needs a Node.js process.

**Fix:** build for Node.js with `preset: 'node'` in the `vite-hub/nuxt` options. Or turn the assistant off for that build, for example `assistant: process.env.NITRO_PRESET !== 'cloudflare-module'`.

### Assistant errors in the panel

The assistant panel shows the errors of its Agent and its Connection, such as `AGENT_R1016` when the ChatGPT grant is missing. See [ChatGPT plan recovery](https://vitehub.dev/docs/connections/chatgpt#recovery), [Connections limits and errors](https://vitehub.dev/docs/connections/limits-and-errors), and [Errors and diagnostics](https://vitehub.dev/docs/reference/errors-diagnostics).