Merge branch 'main' into patch-35

Author: yanthomasdev

.github/actions/install/action.yml

@@ -5,7 +5,7 @@ runs:
   using: composite
   steps:
     - name: Setup PNPM
-      uses: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4.3.0
+      uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v5.0.0
 
     - name: Setup Node
       uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f # v6.3.0

src/content/docs/en/concepts/islands.mdx

@@ -114,7 +114,7 @@ import Avatar from "../components/Avatar.astro";
 
 This breaks up your page with smaller areas of server-rendered content that each load in parallel.
 
-Your page's main content can be rendered immediately with placeholder content, such as a generic avatar until your island's own content is available. With server islands, having small components of personalized content does not delay the rendering of an otherwise static page.
+Your page's main content can be rendered immediately with placeholder content, such as a generic avatar, until your island's own content is available. With server islands, having small components of personalized content does not delay the rendering of an otherwise static page.
 
 This rendering pattern was built to be portable. It does not depend on any server infrastructure so it will work with any host, from a Node.js server in a Docker container to the serverless provider of your choice.
 

src/content/docs/en/editor-setup.mdx

@@ -55,7 +55,6 @@ In addition to local editors, Astro also runs well on in-browser hosted editors,
 
 - [StackBlitz](https://stackblitz.com/) and [CodeSandbox](https://codesandbox.io/) - online editors that run in your browser, with built-in syntax highlighting support for `.astro` files. No installation or configuration required!
 - [GitHub.dev](https://github.dev/) - allows you to install the Astro VS Code extension as a [web extension](https://code.visualstudio.com/api/extension-guides/web-extensions), which gives you access to only some of the full extension features. Currently, only syntax highlighting is supported.
-- [Firebase Studio](https://firebase.studio/) - a full dev environment in the cloud that can install the official Astro VS Code Extension from Open VSX.
 
 ## Other tools
 

src/content/docs/en/guides/build-with-ai.mdx

@@ -283,15 +283,11 @@ Zed doesn't support streaming HTTP, so it requires a local proxy configuration:
 
 #### ChatGPT
 
-:::caution[Limited availability]
-MCP server integration is only available for ChatGPT Pro, Team, and Enterprise users. The setup process is more complex than other tools.
-:::
-
 Refer to the [OpenAI MCP documentation](https://platform.openai.com/docs/mcp#test-and-connect-your-mcp-server) for specific setup instructions.
 
 #### Raycast
 
-[Raycast](https://www.raycast.com/) can connect to MCP servers to enhance its AI capabilities. AI features such as MCP require a [Raycast Pro](https://www.raycast.com/pro) account, so ensure you have upgraded before trying to install. Adding the Astro Docs MCP server allows Raycast to access the latest Astro documentation while answering questions.
+[Raycast](https://www.raycast.com/) can connect to MCP servers to enhance its AI capabilities. Adding the Astro Docs MCP server allows Raycast to access the latest Astro documentation while answering questions.
 
 Install by clicking the button below:
 

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

@@ -174,7 +174,7 @@ Things can sometimes go wrong when setting up the preview. If something's not ri
 * Make sure the site is live - for example, your dev server is running.
 * Make sure that the URLs match exactly - the one in your Astro project and the one set in the Builder app.
 * Make sure it's the full URL including the protocol, for example `https://`.
-* If you're working in a virtual environment like [Firebase Studio](https://studio.firebase.google.com/) or [StackBlitz](https://stackblitz.com/), you might have to copy and paste the URL again when you restart your workspace, since this usually generates a new URL for your project.
+* If you're working in a virtual environment like [StackBlitz](https://stackblitz.com/), you might have to copy and paste the URL again when you restart your workspace, since this usually generates a new URL for your project.
 
 For more ideas, read [Builder's troubleshooting guide](https://www.builder.io/c/docs/guides/preview-url-working).
 :::

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

@@ -256,7 +256,7 @@ You can provide your entries as an array of objects with an `id` property, or in
 
 #### Parsing other data formats
 
-Support for parsing single JSON, YAML, and TOML files into collection entries withe the `file()` loader is built-in (unless you have a [nested JSON document](#nested-json-documents)). To load your collection from unsupported file types, such as `.csv`, you will need to create a [parser function](/en/reference/content-loader-reference/#parser). This function can be made async if required (e.g. to fetch files from the web, or if your parser is asyncronous).
+Support for parsing single JSON, YAML, and TOML files into collection entries with the `file()` loader is built-in (unless you have a [nested JSON document](#nested-json-documents)). To load your collection from unsupported file types, such as `.csv`, you will need to create a [parser function](/en/reference/content-loader-reference/#parser). This function can be made async if required (e.g. to fetch files from the web, or if your parser is asyncronous).
 
 The following example shows importing a third-party CSV parser then passing a custom `parser` function to the `file()` loader:
 
@@ -419,7 +419,7 @@ relatedPosts:
 ---
 ```
 
-These references will be transformed into objects containing a `collection` key and an `id` key, allowing you to easily [query them in your templates](/en/guides/content-collections/#accessing-referenced-data).
+These references will be transformed into objects containing a `collection` key and an `id` key, allowing you to easily [query them in your templates](#accessing-referenced-data).
 
 ## Querying build-time collections
 
@@ -557,7 +557,7 @@ const englishDocsEntries = await getCollection('docs', ({ id }) => {
 
 ### Accessing referenced data
 
-To access [references defined in your schema](/en/guides/content-collections/#defining-collection-references), first query your collection entry. Your references will be available on the returned `data` object. (e.g. `entry.data.author` and `entry.data.relatedPosts`)
+To access [references defined in your schema](#defining-collection-references), first query your collection entry. Your references will be available on the returned `data` object. (e.g. `entry.data.author` and `entry.data.relatedPosts`)
 
 Then, you can use the `getEntry()` function again (or `getEntries()` to retrieve multiple referenced entries) by passing those returned values. The `reference()` function in your schema transforms those values into one or more `collection` and `id` objects as a convenient way to query this related data.
 
@@ -633,7 +633,7 @@ If your custom slugs contain the `/` character to produce URLs with multiple pat
 With an adapter installed for [on-demand rendering](/en/guides/on-demand-rendering/), you can generate your dynamic page routes at request time. First, examine the request (using `Astro.request` or `Astro.params`) to find the slug on demand, and then fetch it using one of Astro's content collection helper functions:
 
 - [`getEntry()`](/en/reference/modules/astro-content/#getentry) for build-time collection pages that are generated once, upon first request.
-- [`getLiveEntry()`](/en/reference/modules/astro-content/#getentry) for live collection pages where data is (re)fetched at each request time.
+- [`getLiveEntry()`](/en/reference/modules/astro-content/#getliveentry) for live collection pages where data is (re)fetched at each request time.
 
 
 ```astro title="src/pages/posts/[id].astro"

src/content/docs/en/guides/deploy/cloudflare.mdx

@@ -13,12 +13,8 @@ import { Steps } from '@astrojs/starlight/components';
 import StaticSsrTabs from '~/components/tabs/StaticSsrTabs.astro';
 import PackageManagerTabs from '~/components/tabs/PackageManagerTabs.astro'
 
-You can deploy full-stack applications, including front-end static assets and back-end APIs, as well as on-demand rendered sites, to both [Cloudflare Workers](https://developers.cloudflare.com/workers/static-assets/) and [Cloudflare Pages](https://pages.cloudflare.com/). 
+You can deploy full-stack applications, including front-end static assets and back-end APIs, as well as on-demand rendered sites, to [Cloudflare Workers](https://developers.cloudflare.com/workers/static-assets/). 
 
-This guide includes:
-
-- [How to deploy to Cloudflare Workers](#cloudflare-workers)
-- [How to deploy to Cloudflare Pages](#cloudflare-pages)
 
 :::note
 
@@ -125,14 +121,14 @@ After your assets are uploaded, Wrangler will give you a preview URL to inspect
 
 ### How to deploy with CI/CD
 
-You can also use a CI/CD system such as [Workers Builds (BETA)](https://developers.cloudflare.com/workers/ci-cd/builds/) to automatically build and deploy your site on push. 
+You can also use a CI/CD system such as [Workers Builds](https://developers.cloudflare.com/workers/ci-cd/builds/) to automatically build and deploy your site on push. 
 
 If you're using Workers Builds:
 
 <Steps>
 1. Follow Steps 1-3 from the Wrangler section above.
 
-2. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and navigate to `Workers & Pages`. Select `Create`.
+2. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and navigate to `Compute > Workers & Pages`. Select `Create application`.
 
 3. Under `Import a repository`, select a Git account and then the repository containing your Astro project.
 
@@ -143,144 +139,6 @@ If you're using Workers Builds:
 5. Click `Save and Deploy`. You can now preview your Worker at its provided `workers.dev` subdomain.
 </Steps>
 
-## Cloudflare Pages
-
-### How to deploy with Wrangler
-
-<Steps>
-1. Install [Wrangler CLI](https://developers.cloudflare.com/workers/wrangler/get-started/).
-
-      <PackageManagerTabs>
-        <Fragment slot="npm">
-        ```sh
-        npm install wrangler@latest --save-dev
-        ```
-        </Fragment>
-        <Fragment slot="pnpm">
-        ```sh
-        pnpm add wrangler@latest --save-dev
-        ```
-        </Fragment>
-        <Fragment slot="yarn">
-        ```sh
-        yarn add wrangler@latest --dev
-        ```
-        </Fragment>
-      </PackageManagerTabs>
-
-2. If your site uses on-demand rendering, install the [`@astrojs/cloudflare` adapter](/en/guides/integrations-guide/cloudflare/). 
-    
-    This will install the adapter and make the appropriate changes to your `astro.config.mjs` file in one step.
-    
-       <PackageManagerTabs>
-        <Fragment slot="npm">
-        ```sh
-        npx astro add cloudflare
-        ```
-        </Fragment>
-        <Fragment slot="pnpm">
-        ```sh
-        pnpm astro add cloudflare
-        ```
-        </Fragment>
-        <Fragment slot="yarn">
-        ```sh
-        yarn astro add cloudflare
-        ```
-        </Fragment>
-      </PackageManagerTabs>
-
-3. Create a [Wrangler configuration file](https://developers.cloudflare.com/workers/wrangler/configuration/).
-
-    Because Cloudflare recommends new projects use Workers instead of Pages, the `astro add cloudflare` command creates a `wrangler.jsonc` and `public/.assetsignore` file, which are specific to Workers projects. You will need to delete the `public/.assetsignore` file and change your `wrangler.jsonc` file. If you are not using the adapter you'll need to create it yourself.
-
-    Ensure your `wrangler.jsonc` file is structured like this:
-
-    <StaticSsrTabs>
-      <Fragment slot="static">
-      ```jsonc title="wrangler.jsonc"
-      {
-        "name": "my-astro-app",
-        "compatibility_date": "YYYY-MM-DD", // Update to the day you deploy
-        "pages_build_output_dir": "./dist"
-      }
-      ```
-      </Fragment>
-      <Fragment slot="ssr">
-        ```jsonc title="wrangler.jsonc"
-        {
-          "name": "my-astro-app",
-          "compatibility_date": "YYYY-MM-DD", // Update to the day you deploy
-          "compatibility_flags": [
-            "nodejs_compat",
-            "disable_nodejs_process_v2"
-          ],
-          "pages_build_output_dir": "./dist"
-        }
-        ```
-      </Fragment>
-    </StaticSsrTabs>
-
-    <ReadMore>Read more about [on-demand rendering in Astro](/en/guides/on-demand-rendering/).</ReadMore>
-
-3. Preview your project locally with Wrangler.
-
-      <PackageManagerTabs>
-        <Fragment slot="npm">
-        ```sh
-        npx astro build && wrangler pages dev ./dist
-        ```
-        </Fragment>
-        <Fragment slot="pnpm">
-        ```sh
-        pnpm astro build && wrangler pages dev ./dist
-        ```
-        </Fragment>
-        <Fragment slot="yarn">
-        ```sh
-        yarn astro build && wrangler pages dev ./dist
-        ```
-        </Fragment>
-      </PackageManagerTabs>
-
-4. Deploy using `npx wrangler deploy`.
-
-      <PackageManagerTabs>
-        <Fragment slot="npm">
-        ```sh
-        npx astro build && wrangler pages deploy ./dist
-        ```
-        </Fragment>
-        <Fragment slot="pnpm">
-        ```sh
-        pnpm astro build && wrangler pages deploy ./dist
-        ```
-        </Fragment>
-        <Fragment slot="yarn">
-        ```sh
-        yarn astro build && wrangler pages deploy ./dist
-        ```
-        </Fragment>
-      </PackageManagerTabs>
-</Steps>
-
-After your assets are uploaded, Wrangler will give you a preview URL to inspect your site.
-
-### How to deploy a site with CI/CD
-
-<Steps>
-1. Push your code to your git repository (e.g. GitHub, GitLab).
-
-2. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and navigate to **Compute (Workers) > Workers & Pages**. Select **Create** and then select the **Pages** tab. Connect your git repository.
-
-3. Configure your project with:
-    - **Framework preset**: `Astro`
-    - **Build command:** `npm run build`
-    - **Build output directory:** `dist`
-    
-4. Click the **Save and Deploy** button.
-</Steps>
-
 ## Troubleshooting
 
 ### 404 behavior
@@ -296,8 +154,6 @@ For Workers projects, you will need to set `not_found_handling` if you want to s
 }
 ```
 
-For Pages projects, if you include a custom 404 page, it will be served by default. Otherwise, Pages will default to [Cloudflare's single-page application rendering behavior](https://developers.cloudflare.com/pages/configuration/serving-pages/#single-page-application-spa-rendering) and redirect to the home page instead of showing a 404 page.
-
 ### Client-side hydration
 
 Client-side hydration may fail as a result of Cloudflare's Auto Minify setting. If you see `Hydration completed but contains mismatches` in the console, make sure to disable Auto Minify under Cloudflare settings.

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

@@ -64,7 +64,7 @@ This example will demonstrate adding a custom font using the font file `DistantG
 
 Astro supports [several font providers](/en/reference/font-provider-reference/#built-in-providers) out of the box, including support for [Fontsource](https://fontsource.org/) that simplifies using Google Fonts and other open-source fonts.
 
-The following example will use Fontsource to add custom font support, but the process is similar for any of Astro's built-in font providers (e.g. [Adobe](https://fonts.adobe.com/), [Bunny](https://fonts.bunny)).
+The following example will use Fontsource to add custom font support, but the process is similar for any of Astro's built-in font providers (e.g. [Adobe](https://fonts.adobe.com/), [Bunny](https://fonts.bunny.net/)).
 
 <Steps>
 
@@ -102,7 +102,7 @@ After [a font is configured](#configuring-custom-fonts), it must be added to you
 
     <html>
       <head>
-        <Font cssVariable="--font-distant-galaxy" preload />
+        <Font cssVariable="--font-distant-galaxy" />
       </head>
       <body>
         <slot />
@@ -125,7 +125,7 @@ After [a font is configured](#configuring-custom-fonts), it must be added to you
 
       <style>
       h1 {
-        font-family: var("--font-distant-galaxy");
+        font-family: var(--font-distant-galaxy);
       }
       </style>
     </Layout>
@@ -147,7 +147,7 @@ Instead, after [configuring your custom font](#configuring-custom-fonts) and [ad
     @import "tailwindcss";
 
     @theme inline {
-        --font-sans: var(--font-roboto);
+      --font-sans: var(--font-roboto);
     }
     ```
 
@@ -158,22 +158,22 @@ Instead, after [configuring your custom font](#configuring-custom-fonts) and [ad
     ```js title="tailwind.config.mjs" ins={6-8}
     /** @type {import("tailwindcss").Config} */
     export default {
-    content: ["./src/**/*.{astro,html,js,jsx,md,mdx,svelte,ts,tsx,vue}"],
-    theme: {
+      content: ["./src/**/*.{astro,html,js,jsx,md,mdx,svelte,ts,tsx,vue}"],
+      theme: {
         extend: {},
         fontFamily: {
-            sans: ["var(--font-roboto)"]
+          sans: ["var(--font-roboto)"]
         }
-    },
-    plugins: []
+      },
+      plugins: []
     };
     ```
 
     </TabItem>
 
     </Tabs>
 
-See [Tailwind's docs on adding custom font families](https://tailwindcss.com/docs/font-family#using-custom-values) for more information.
+See [Tailwind's docs on adding custom font families](https://tailwindcss.com/docs/font-family#using-a-custom-value) for more information.
 
 
 ## Accessing font data programmatically
@@ -261,7 +261,7 @@ export default defineConfig({
       provider: fontProviders.google(),
       // Default included:
       // weights: [400] ,
-      // styles: ["normal", "italics"],
+      // styles: ["normal", "italic"],
       // subsets: ["latin"],
       // fallbacks: ["sans-serif"], 
       // formats: ["woff2"],