# DOCS_CONTENT_INVALID

<!-- Generated by docs/modules/diagnostics from the package catalogs. Write a guide in docs/diagnostics/<CODE>.md instead of editing this file. -->

Page frontmatter 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 it happens

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

## Fix it

Correct the named field. 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.

## Source

`DOCS_CONTENT_INVALID` belongs to the `docs` package. Its catalog entry is in [`src/error-diagnostics.ts`](https://github.com/vite-hub/vitehub/blob/main/packages/docs/src/error-diagnostics.ts#L24). It is raised in [`src/manifest.ts`](https://github.com/vite-hub/vitehub/blob/main/packages/docs/src/manifest.ts#L82).

See [all Docs site diagnostics](https://vitehub.dev/docs/docs-site/diagnostics).

<!-- vitehub-docs:section-links -->
## In this section

- [Overview](https://vitehub.dev/raw/docs/docs-site.md)
- [Get started](https://vitehub.dev/raw/docs/docs-site/get-started.md)
- [Add to a Nuxt app](https://vitehub.dev/raw/docs/docs-site/nuxt-app.md)
- [Configure](https://vitehub.dev/raw/docs/docs-site/configure.md)
- [Docs assistant](https://vitehub.dev/raw/docs/docs-site/assistant.md)
- [Server API](https://vitehub.dev/raw/docs/docs-site/server-api.md)
- [Limits and errors](https://vitehub.dev/raw/docs/docs-site/limits-and-errors.md)

Next: [DOCS_EXAMPLE_MISSING](https://vitehub.dev/raw/docs/docs-site/diagnostics/docs_example_missing.md)

All pages: [llms.txt](https://vitehub.dev/llms.txt)
