docs: update broken links

Author: farnabaz

docs/content/docs/1.getting-started/1.index.md

@@ -12,13 +12,13 @@ Welcome to Nuxt Content v3, a major upgrade that brings enhanced performance and
 
 Collections organize related items within your project, helping you manage large datasets more efficiently. Key benefits include:
 
-- **Structured Data**: Configure database architecture and define collections in [`content.config.ts`](/docs/getting-started/collections#defining-collections)
+- **Structured Data**: Configure database architecture and define collections in [`content.config.ts`](/docs/collections/collections#defining-collections)
 - **Type-safe Queries**: Direct TypeScript integration across all utilities
 - **Automatic Validation**: Ensure data consistency across frontmatter fields and data files (json, yml...)
 - **Advanced Query Builder**: Filter, sort, and paginate your collections with ease
 - **Studio Integration**: Enhanced form generation and optimal editing experience through [Studio](https://nuxt.studio)
 
-Learn more about [Content Collections](/docs/getting-started/collections).
+Learn more about [Content Collections](/docs/collections/collections).
 
 ### Improved Performance
 

docs/content/docs/1.getting-started/2.installation.md

@@ -58,7 +58,7 @@ This configuration creates a default `content` collection that processes all Mar
 The `type: page` means there is a 1-to-1 relationship between content files and pages on your site.
 ::
 
-::note{to="/docs/collections/define"}
+::note{to="/docs/collections/collections"}
 Learn more in our **Collections guide**.
 ::
 

docs/content/docs/1.getting-started/4.migration.md

@@ -25,7 +25,7 @@ Here is the list breaking changes in Content v3:
 - Multi source is dropped in favor of multi collection.
 - Document `._path` is now renamed to `.path`
 - `searchContent()`{lang=ts} is dropped in favor of new api `queryCollectionSearchSections`
-  - Full text search can easily done using this API See [Full-Text Search Snippets](/docs/snippets/fulltext-search)
+  - Full text search can easily done using this API See [Full-Text Search Snippets](/docs/advanced/fulltext-search)
 - `useContentHelpers()`{lang=ts} is removed
 
 

docs/content/docs/2.collections/1.collections.md

@@ -95,7 +95,7 @@ const { data: posts } = await useAsyncData('blog', () => queryCollection('blog')
 </template>
 ```
 
-::note{to="/api/query-collection"}
+::note{to="/docs/utils/query-collection"}
 Learn more about the available query options in our `queryCollections` API documentation.
 ::
 

docs/content/docs/2.collections/2.types.md

@@ -40,7 +40,7 @@ Here are examples of generated paths based on file structure:
 | `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.
+You can use the helper [`queryCollection('COLLECTION').path('PATH')`{lang=ts}](/docs/utils/query-collection) to retrieve content by a specific path.
 ::
 
 ### Schema Overrides
@@ -52,7 +52,7 @@ When you use the **page** type, Nuxt Content generates several standard fields t
 - `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))
+- `navigation`: Page navigation configuration (for [queryCollectionNavigation](/docs/utils/query-collection-navigation))
 
 Here is the corresponding schema applied:
 ```ts

docs/content/docs/3.files/1.markdown.md

@@ -89,7 +89,7 @@ description: 'meta description of the page'
 | ------------------------------------------- | :-------: | ------------------------------------- | -------------------------------------------------------------------------------------------------------- |
 | `title`                                     | `string`  | First `<h1>`{lang="html"} of the page | Title of the page, will also be injected in metas                                                        |
 | `description`                               | `string`  | First `<p>`{lang="html"} of the page  | Description of the page, will be shown below the title and injected into the metas                       |
-| `navigation`                                | `boolean` | `true`                                | Define if the page is included in [`queryCollectionNavigation`](/docs/usage/navigation) return value. |
+| `navigation`                                | `boolean` | `true`                                | Define if the page is included in [`queryCollectionNavigation`](/docs/utils/query-collection-navigation) return value. |
 
 
 ## Excerpt
@@ -131,7 +131,7 @@ Code highlighting works both on [`ProsePre`](/docs/components/prose#prosepre) an
 Each line of a code block gets its line number in the `line` attribute so lines can be labeled or individually styled.
 
 ::callout
-[Read the API reference to configure or entirely disable syntax highlighting.](/get-started/configuration)
+[Read the API reference to configure or entirely disable syntax highlighting.](/docs/getting-started/configuration)
 ::
 
 ## Images
@@ -473,7 +473,7 @@ Code highlighting works both on [`ProsePre`](/docs/components/prose#prosepre) an
 Each line of a code block gets its line number in the `line` attribute so lines can be labeled or individually styled.
 
 ::callout
-[Read the API reference to configure or entirely disable syntax highlighting.](/get-started/configuration)
+[Read the API reference to configure or entirely disable syntax highlighting.](/docs/getting-started/configuration)
 ::
 
 ### Images

docs/content/docs/3.utils/1.query-collection.md

@@ -11,7 +11,7 @@ function queryCollection<T extends keyof Collections>(collection: T): Collection
 
 ## Usage
 
-Use the auto-imported `queryCollection` to find contents inside a collection.Here we assume that you havr defined `docs` collection inside `content.config.ts`. If you have not defined any collection, check [How to define a collection](/docs/getting-started/collections#defineCollection).
+Use the auto-imported `queryCollection` to find contents inside a collection.Here we assume that you havr defined `docs` collection inside `content.config.ts`. If you have not defined any collection, check [How to define a collection](/docs/collections/collections#defining-collections).
 
 ```vue [pages/[...slug\\].vue]
 <script>

docs/content/docs/3.utils/2.query-collection-navigation.md

@@ -34,4 +34,4 @@ Generate a navigation tree for the specified collection.
 
 - Returns: A Promise that resolves to a navigation tree structure.
 
-The navigation tree is generated based on the directory structure and ordering happens based on files [ordering](/docs/getting-started/contents#ordering)
+The navigation tree is generated based on the directory structure and ordering happens based on files [ordering](/docs/collections/types#ordering-files)