[v6] New content collections guide includes live collections

src/content/docs/en/guides/cms/keystatic.mdx

@@ -183,7 +183,7 @@ Visit `http://127.0.0.1:4321/keystatic` in the browser to see the Keystatic Admi
 
 ## Rendering Keystatic content
 
-Use Astro's Content Collections API to [query and display your posts and collections](/en/guides/content-collections/#querying-collections), just as you would in any Astro project.
+[Query and display your posts and collections](/en/guides/content-collections/#querying-build-time-collections), just as you would in any Astro project.
 
 ### Displaying a collection list
 

src/content/docs/en/guides/imports.mdx

@@ -344,7 +344,7 @@ Additionally, glob patterns must begin with one of the following:
 
 ### `import.meta.glob()` vs `getCollection()`
 
-[Content collections](/en/guides/content-collections/) provide a [`getCollection()` API](/en/reference/modules/astro-content/#getcollection) for loading multiple files instead of `import.meta.glob()`. If your content files (e.g. Markdown, MDX, Markdoc) are located in collections within the `src/content/` directory, use `getCollection()` to [query a collection](/en/guides/content-collections/#querying-collections) and return content entries.
+[Content collections](/en/guides/content-collections/) provide [performant, content-focused APIs](/en/reference/modules/astro-content/) for loading multiple files instead of `import.meta.glob()`. Use `getCollection()` and `getLiveCollection()` to query your collections and return content entries.
 
 ## WASM
 

src/content/docs/en/guides/integrations-guide/markdoc.mdx

@@ -113,7 +113,7 @@ Markdoc files can only be used within content collections. Add entries to any co
       - quick-start.mdoc
 </FileTree>
 
-Then, query your collection using the [Content Collection APIs](/en/guides/content-collections/#querying-collections):
+Then, [query and display your posts and collections](/en/guides/content-collections/#querying-build-time-collections):
 
 ```astro title="src/pages/why-markdoc.astro"
 ---

src/content/docs/en/guides/integrations-guide/mdx.mdx

@@ -96,9 +96,9 @@ It also adds extra features to standard MDX, including support for Markdown-styl
 
 `.mdx` files must be written in [MDX syntax](https://mdxjs.com/docs/what-is-mdx/#mdx-syntax) rather than Astro’s HTML-like syntax.
 
-### Using MDX with content collections
+### Using local MDX with content collections
 
-To include MDX files in a content collection, make sure that your [collection loader](/en/guides/content-collections/#defining-the-collection-loader) is configured to load content from `.mdx` files:
+To include your local MDX files in a content collection, make sure that your [collection loader](/en/guides/content-collections/#build-time-collection-loaders) is configured to load content from `.mdx` files:
 
 ```js title="src/content.config.ts" ins="mdx"
 import { defineCollection, z } from 'astro:content';

src/content/docs/en/guides/markdown-content.mdx

@@ -399,7 +399,7 @@ When using the frontmatter `layout` property, you must include the `<meta charse
 
 Astro's internal Markdown processor is not available for processing remote Markdown.
 
-To fetch remote Markdown for use in [content collections](/en/guides/content-collections/), you can [build a custom loader](/en/guides/content-collections/#building-a-custom-loader) with access to a [`renderMarkdown()` function](/en/reference/content-loader-reference/#rendermarkdown).
+To fetch remote Markdown for use in [content collections](/en/guides/content-collections/), you can [build a custom loader](/en/guides/content-collections/#custom-build-time-loaders) with access to a [`renderMarkdown()` function](/en/reference/content-loader-reference/#rendermarkdown).
 
 To fetch remote Markdown directly and render it to HTML, you will need to install and configure your own Markdown parser from NPM. This will not inherit from any of Astro's built-in Markdown settings that you have configured.
 

src/content/docs/en/guides/media/cloudinary.mdx

@@ -134,7 +134,7 @@ export const collections = {
 }
 ```
 
-You can then use the [`getCollection()` or `getEntry()` query functions](/en/guides/content-collections/#querying-collections) to select one or many images or videos from your collection.
+You can then use the [`getCollection()` or `getEntry()` query functions](/en/guides/content-collections/#querying-build-time-collections) to select one or many images or videos from your collection.
 
 See [Cloudinary's `cldAssetsLoader` documentation](https://astro.cloudinary.dev/cldassetsloader/basic-usage) for more information.
 

src/content/docs/en/guides/migrate-to-astro/from-create-react-app.mdx

@@ -349,7 +349,7 @@ const randomUser = data.results[0];
 ---
 ```
 
-See more about local files imports with [`import.meta.glob()`](/en/guides/imports/#importmetaglob), [querying using the Collections API](/en/guides/content-collections/#querying-collections) or [fetching remote data](/en/guides/data-fetching/).
+See more about local files imports with [`import.meta.glob()`](/en/guides/imports/#importmetaglob), [querying with content collections](/en/guides/content-collections/#querying-build-time-collections) or [fetching remote data](/en/guides/data-fetching/).
 
 ### CRA Styling to Astro
 

src/content/docs/en/guides/migrate-to-astro/from-gatsby.mdx

@@ -36,7 +36,7 @@ When you rebuild your Gatsby site in Astro, you will notice some important diffe
 
 - [Astro components](/en/basics/astro-components/) are not written as exported functions that return page templating. Instead, you'll split your code into a "code fence" for your JavaScript and a body exclusively for the HTML you generate.
 
-- [Local file data](/en/guides/imports/): Gatsby uses GraphQL to retrieve data from your project files. Astro uses ESM imports and top-level await functions (e.g. [`import.meta.glob()`](/en/guides/imports/#importmetaglob), [`getCollection()`](/en/guides/content-collections/#querying-collections)) to import data from your project files. You can manually add GraphQL to your Astro project but it is not included by default.
+- [Local file data](/en/guides/imports/): Gatsby uses GraphQL to retrieve data from your project files. Astro uses ESM imports and top-level await functions (e.g. [`import.meta.glob()`](/en/guides/imports/#importmetaglob), [`getCollection()`](/en/guides/content-collections/#querying-build-time-collections)) to import data from your project files. You can manually add GraphQL to your Astro project but it is not included by default.
 
 ## Convert your Gatsby Project
 

src/content/docs/en/guides/migrate-to-astro/from-nextjs.mdx

@@ -405,7 +405,7 @@ const randomUser = data.results[0];
 ---
 ```
 
-See more about local files imports with [`import.meta.glob()`](/en/guides/imports/#importmetaglob), [querying using the Collections API](/en/guides/content-collections/#querying-collections) or [fetching remote data](/en/guides/data-fetching/).
+See more about local files imports with [`import.meta.glob()`](/en/guides/imports/#importmetaglob), [querying with content collections](/en/guides/content-collections/#querying-build-time-collections) or [fetching remote data](/en/guides/data-fetching/).
 
 ### Next Styling to Astro
 

src/content/docs/en/guides/upgrade-to/v6.mdx

@@ -194,7 +194,7 @@ If you have [content collections errors](/en/reference/error-reference/#content-
 
 <details>
 <summary>no content collections configuration file</summary>
-Create `src/content.config.ts` and [define your collections](/en/guides/content-collections/#defining-collections) in it.
+Create `src/content.config.ts` and [define your collections](/en/guides/content-collections/#build-time-content-collections) in it.
 </details>
 
 <details>
@@ -205,7 +205,7 @@ Rename and move this file to `src/content.config.ts`
 <details>
 <summary>a collection that does not define a `loader`/ ([`ContentCollectionMissingALoaderError`](/en/reference/errors/content-collection-missing-loader/))</summary>
 
-Import [Astro's built-in `glob()` loader](/en/guides/content-collections/#built-in-loaders) and define the `pattern` and `base` for your collection entries:
+Import [Astro's built-in `glob()` loader](/en/guides/content-collections/#the-glob-loader) and define the `pattern` and `base` for your collection entries:
 
 ```ts ins={3,6}
 // src/content.config.ts

src/content/docs/en/reference/cli-reference.mdx

@@ -410,7 +410,7 @@ astro --config config/astro.config.mjs dev
 
 <p><Since v="5.0.0" /></p>
 
-Clear the [content layer cache](/en/guides/content-collections/#defining-the-collection-loader), forcing a full rebuild.
+Clear the content layer cache, forcing a full rebuild.
 
 ### `--mode <string>`