docs: update

Author: larbish

docs/app/pages/docs/[...slug].vue

@@ -16,7 +16,7 @@ const { data } = await useAsyncData(route.path, () => Promise.all([
 ]), {
   transform: ([page, surround]) => ({ page, surround }),
 })
-if (!data.value) {
+if (!data.value || !data.value.page) {
   throw createError({ statusCode: 404, statusMessage: 'Page not found', fatal: true })
 }
 

docs/content/docs/2.collections/.navigation.yml

@@ -0,0 +1,3 @@
+
+title: Collections
+icon: i-lucide-database

…cs/content/docs/2.usage/1.collections.md …tent/docs/2.collections/1.collections.mddocs/content/docs/2.usage/1.collections.md renamed to docs/content/docs/2.collections/1.collections.md docs/content/docs/2.usage/1.collections.md renamed to docs/content/docs/2.collections/1.collections.md

@@ -1,5 +1,5 @@
 ---
-title: Define Collections
+title: Define
 description: 'Learn how to define and configure content collections in your Nuxt application.'
 ---
 
@@ -43,11 +43,6 @@ export const collections = {
 }
 ```
 
-
-::note{to="/docs/usage/types"}
-Learn more about collection types.
-::
-
 ### Collection Schema
 
 Schemas enforce data consistency within a collection and serve as the source of truth for TypeScript types.
@@ -119,7 +114,13 @@ type Collection = {
   // Zod schema for content validation and typing
   schema?: ZodObject<T>
 }
+```
 
+::note{to="/docs/usage/types"}
+Learn more about collection types.
+::
+
+```ts
 type CollectionSource = {
   // Glob pattern for content matching
   include: string
@@ -134,24 +135,8 @@ type CollectionSource = {
 }
 ```
 
-### Built-in Fields
-
-Every collection includes these default fields:
-
-- `id`: Unique content identifier
-- `stem`: File path without extension (used for sorting and location)
-- `extension`: File extension
-- `meta`: Custom fields not defined in the collection schema
-
-Additional fields for `page` type collections:
-
-- `path`: Generated route path
-- `title`: Page title
-- `description`: Page description
-- `seo`: SEO metadata (to be used with Nuxt's `useSeoMeta` composable)
-- `body`: Page content parsed as AST
-- `navigation`: Page navigation configuration (for [`queryCollectionNavigation](/docs/composables/query-collection-navigation))
-
-### Returns
+::note{to="/docs/usage/sources"}
+Learn more about collection sources.
+::
 
 The function returns the defined collection object.

docs/content/docs/2.usage/2.types.md …cs/content/docs/2.collections/2.types.mddocs/content/docs/2.usage/2.types.md renamed to docs/content/docs/2.collections/2.types.md docs/content/docs/2.usage/2.types.md renamed to docs/content/docs/2.collections/2.types.md

@@ -1,10 +1,17 @@
 ---
-title: Collection types
+title: Types
 description: Learn about the two types of collections you can define in Nuxt Content.
 ---
 
 In Nuxt Content, you can specify a type for each collection, depending on the intended purpose of the collection files. Collections can be defined as either **page** or **data** types.
 
+For both types, built-in fields are generated. Every collection includes these default fields:
+
+- `id`: Unique content identifier
+- `stem`: File path without extension (used for sorting and location)
+- `extension`: File extension
+- `meta`: Custom fields not defined in the collection schema
+
 ## Page type
 
 ```ts
@@ -14,7 +21,9 @@ defineCollection({
 })
 ```
 
+::tip
 Use the **page** type if there is a 1-to-1 relationship between content files and pages on your site. 
+::
 
 ### Path generation
 
@@ -30,20 +39,26 @@ Here are examples of generated paths based on file structure:
 | `content/blog/hello.md`          | `/blog/hello`         |
 | `content/1.guide/2.installation` | `/guide/installation` |
 
-
+::note
 You can use the helper [`queryCollection('COLLECTION').path('PATH')`{lang=ts}](/composables/query-collection) to retrieve content by a specific path.
+::
 
 ### Schema Overrides
 
 When you use the **page** type, Nuxt Content generates several standard fields that are commonly used for web pages. These fields provide structure and are **automatically** applied to the collection’s schema:
+
+- `path`: Generated route path
+- `title`: Page title
+- `description`: Page description
+- `seo`: SEO metadata (to be used with Nuxt's `useSeoMeta` composable)
+- `body`: Page content parsed as AST
+- `navigation`: Page navigation configuration (for [queryCollectionNavigation](/docs/composables/query-collection-navigation))
+
+Here is the corresponding schema applied:
 ```ts
-  // Generated path of your file
   path: z.string(),
-  // Title of your page
   title: z.string(),
-  // Description of your page
   description: z.string(),
-  // Seo information
   seo: z.intersection(
     z.object({
       title: z.string().optional(),
@@ -53,13 +68,11 @@ When you use the **page** type, Nuxt Content generates several standard fields t
     }),
     z.record(z.string(), z.any()),
   ).optional().default({}),
-  // AST of your markdown parsed (only useful for Markdown files)
   body: z.object({
     type: z.string(),
     children: z.any(),
     toc: z.any(),
   }),
-  // Navigation information
   navigation: z.union([
     z.boolean(),
     z.object({
@@ -74,9 +87,26 @@ When you use the **page** type, Nuxt Content generates several standard fields t
 You can override any of these fields by defining them in the collection’s schema.
 ::
 
-### Ordering Files
+## Data type
 
-Since each file corresponds to a page, you may want to control the display order in lists. Use numeric prefixes in file and directory names to specify an order. Nuxt Content will use these numbers when ordering content lists.
+```ts
+defineCollection({
+  source: 'authors/**.yml',
+  type: 'data'
+})
+```
+
+The data type is useful for content that doesn’t directly correspond to a webpage but instead represents structured data you might want to query and display within your application.
+
+With data collections, you have complete control over the schema, allowing you to define custom structures.
+
+::note
+There’s no strict relationship between collection type and file extension. For instance, a **page** collection can use [Markdown](/docs/usage/markdown) or [YAML](/docs/usage/yaml) or JS[Markdown](/docs/usage/json) files, and **data** collections can use any of these formats as well. 
+::
+
+## Ordering Files
+
+For both types, you may want to control the display order in lists. Use numeric prefixes in file and directory names to specify an order. Nuxt Content will use these numbers when ordering content lists.
 
 ``` [Directory structure]
 content/
@@ -94,19 +124,3 @@ content/
 Separate number from file name using `.` character. Using any other separator will not work.
 ::
 
-## Data type
-
-```ts
-defineCollection({
-  source: 'authors/**.yml',
-  type: 'data'
-})
-```
-
-The data type is useful for content that doesn’t directly correspond to a webpage but instead represents structured data you might want to query and display within your application.
-
-With data collections, you have complete control over the schema, allowing you to define custom structures.
-
-::note
-There’s no strict relationship between collection type and file extension. For instance, a **page** collection can use [Markdown](/docs/usage/markdown) or [YAML](/docs/usage/yaml) or JS[Markdown](/docs/usage/json) files, and **data** collections can use any of these formats as well. 
-::

docs/content/docs/2.collections/3.sources.md

@@ -0,0 +1,50 @@
+---
+title: Sources
+description: Learn how to import your files in Nuxt Content collections.
+---
+
+Nuxt Content provides several ways to import content files into your collection. You can configure the source by using the `source` property within `defineCollection`:
+
+```ts [content.config.ts]
+import { defineCollection } from '@nuxt/content'
+
+export const collections = {
+  docs: defineCollection({
+    source: '**',
+    type: 'page'
+  })
+}
+```
+
+## `source`
+
+The `source` property can be defined as either a string (following a glob pattern) or an object, allowing more detailed source configuration for your target directory and files within the content folder.
+
+**Example:**
+- `source: '**` includes all files within the content directory and its subdirectories.
+- `source: '**/*.md'`includes all `Markdown` files within the content directory and its subdirectories.
+- `source: 'docs/**/*.yml'` includes all `YML` files within the `content/docs` and its subdirectories.
+- `source: '**/*.{json,yml}'` includes `JSON` or `YML` file within the content directory and all its subdirectories.
+- `source: '*.json'` includes only `JSON` files located directly within the content directory, excluding any subdirectories.
+
+### `include`
+
+Glob pattern of your target repository and files in the content folder.
+
+### `exclude`
+
+Glob patterns to exclude content from the import.
+
+### `prefix`
+
+This configuration only applied for **page** type with 1-to-1 relationship between content files and pages on your site.
+
+It represents the path prefix (base URL) of the corresponding page on the website. 
+
+### `cwd`
+
+Root directory for content matching.
+
+### `repository`
+
+External source representing a remote git repository URL (e.g., https://github.com/nuxt/content)

docs/content/docs/2.usage/.navigation.yml

@@ -0,0 +1,3 @@
+
+title: Files
+icon: i-lucide-file