Nuxt Content
Workflow
- Inspect the installed
@nuxt/content version, content.config.ts, matching files under content/, and the Nuxt surface that consumes them. The branch is understood when the collection, source glob, schema, and consumer agree.
- Open the smallest matching guide below. Apply Nuxt Content guidance only to content-owned APIs; use Nuxt, Nuxt Studio, Nuxt UI, or Vue guidance when those packages own the remaining surface.
- Implement with typed collections and payload-backed Nuxt data loading. The change is complete when collection types resolve, the intended query returns the expected document shape, and the rendered route works in the target rendering mode.
Routing
| Task |
Open |
| Collection types, schemas, indexes, local/remote sources, or locale prefixes |
Collections |
| Filtering, sorting, pagination, navigation, surroundings, or search |
Querying |
Markdown, MDC, ContentRenderer, prose components, or code highlighting |
Rendering |
| Database adapters, markdown processing, renderer aliases, or deployment storage |
Configuration |
| Hooks, transformers, custom sources, raw content, debugging, or Content v2 migration |
Advanced |
| Visual editing, authentication, media, drafts, or Git publishing |
nuxt-studio skill |
| Writing or restructuring documentation prose |
document-writer skill |
Baseline
// content.config.ts
import { defineCollection, defineContentConfig } from '@nuxt/content'
import { z } from 'zod'
export default defineContentConfig({
collections: {
docs: defineCollection({
type: 'page',
source: 'docs/**',
schema: z.object({
updatedAt: z.date().optional(),
}),
}),
},
})
<script setup lang="ts">
const route = useRoute()
const { data: page } = await useAsyncData(route.path, () => {
return queryCollection('docs').path(route.path).first()
})
</script>
<template>
<ContentRenderer v-if="page" :value="page" />
</template>
Use npx nuxi typecheck to verify generated collection types. When a query is empty, confirm that its collection source includes the file—especially .navigation.yml—before changing query logic.
1---2name: nuxt-content3description: Build typed, content-driven Nuxt applications with @nuxt/content. Use when working with content.config.ts, collections, queryCollection, Markdown or MDC rendering, content databases, hooks, custom sources, search, or Content v2 migrations.4license: MIT5---6
7# Nuxt Content
8
9## Workflow
10
111. Inspect the installed `@nuxt/content` version, `content.config.ts`, matching files under `content/`, and the Nuxt surface that consumes them. The branch is understood when the collection, source glob, schema, and consumer agree.
122. Open the smallest matching guide below. Apply Nuxt Content guidance only to content-owned APIs; use Nuxt, Nuxt Studio, Nuxt UI, or Vue guidance when those packages own the remaining surface.
133. Implement with typed collections and payload-backed Nuxt data loading. The change is complete when collection types resolve, the intended query returns the expected document shape, and the rendered route works in the target rendering mode.
14
15## Routing
16
17| Task | Open |
18| ------------------------------------------------------------------------------------ | ---------------------------------------- |
19| Collection types, schemas, indexes, local/remote sources, or locale prefixes | [Collections](references/collections.md) |
20| Filtering, sorting, pagination, navigation, surroundings, or search | [Querying](references/querying.md) |
21| Markdown, MDC, `ContentRenderer`, prose components, or code highlighting | [Rendering](references/rendering.md) |
22| Database adapters, markdown processing, renderer aliases, or deployment storage | [Configuration](references/config.md) |
23| Hooks, transformers, custom sources, raw content, debugging, or Content v2 migration | [Advanced](references/advanced.md) |
24| Visual editing, authentication, media, drafts, or Git publishing | `nuxt-studio` skill |
25| Writing or restructuring documentation prose | `document-writer` skill |
26
27## Baseline
28
29```ts
30// content.config.ts
31import { defineCollection, defineContentConfig } from '@nuxt/content'
32import { z } from 'zod'
33
34export default defineContentConfig({
35 collections: {
36 docs: defineCollection({
37 type: 'page',
38 source: 'docs/**',
39 schema: z.object({
40 updatedAt: z.date().optional(),
41 }),
42 }),
43 },
44})
45```
46
47```vue
48<script setup lang="ts">
49const route = useRoute()
50const { data: page } = await useAsyncData(route.path, () => {
51 return queryCollection('docs').path(route.path).first()
52})
53</script>
54
55<template>
56 <ContentRenderer v-if="page" :value="page" />
57</template>
58```
59
60Use `npx nuxi typecheck` to verify generated collection types. When a query is empty, confirm that its collection source includes the file—especially `.navigation.yml`—before changing query logic.
onmax