Merge branch 'main' into i18n/fr-update-guides/astro-db.mdx

Author: thomasbnt

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

@@ -569,6 +569,73 @@ const { Content } = await render(post);
 Explore the `src/pages/` folder of the [blog tutorial demo code on GitHub](https://github.com/withastro/blog-tutorial-demo/tree/content-collections/src/pages) to see full examples of creating pages from your collections for blog features like a list of blog posts, tags pages, and more!
 :::
 
+## Collection JSON Schemas
+
+<p><Since v="4.13.0" /></p>
+
+Astro auto-generates [JSON Schema](https://json-schema.org/) files for collections, which you can use in your editor to get IntelliSense and type-checking for data files.
+
+A JSON Schema file is generated for each collection in your project and output to the `.astro/collections/` directory.
+For example, if you have two collections, one named `authors` and another named `posts`, Astro will generate `.astro/collections/authors.schema.json` and `.astro/collections/posts.schema.json`.
+
+### Use JSON Schemas in JSON files
+
+You can manually point to an Astro-generated schema by setting the `$schema` field in your JSON file.
+The value should be a relative file path from the data file to the schema.
+In the following example, a data file in `src/data/authors/` uses the schema generated for the `authors` collection:
+
+```json title="src/data/authors/armand.json" ins={2}
+{
+  "$schema": "../../../.astro/collections/authors.schema.json",
+  "name": "Armand",
+  "skills": ["Astro", "Starlight"]
+}
+```
+
+#### Use a schema for a group of JSON files in VS Code
+
+In VS Code, you can configure a schema to apply for all files in a collection using the [`json.schemas` setting](https://code.visualstudio.com/docs/languages/json#_json-schemas-and-settings).
+In the following example, all files in the `src/data/authors/` directory will use the schema generated for the `authors` collection:
+
+```json
+{
+  "json.schemas": [
+    {
+      "fileMatch": ["/src/data/authors/**"],
+      "url": "./.astro/collections/authors.schema.json"
+    }
+  ]
+}
+```
+
+### Use schemas in YAML files in VS Code
+
+In VS Code, you can add support for using JSON schemas in YAML files using the [Red Hat YAML](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml) extension.
+With this extension installed, you can reference a schema in a YAML file using a special comment syntax:
+
+```yaml title="src/data/authors/armand.yml" ins={1}
+# yaml-language-server: $schema=../../../.astro/collections/authors.schema.json
+name: Armand
+skills:
+  - Astro
+  - Starlight
+```
+
+#### Use schemas for a group of YAML files in VS Code
+
+With the Red Hat YAML extension, you can configure a schema to apply for all YAML files in a collection using the `yaml.schemas` setting.
+In the following example, all YAML files in the `src/data/authors/` directory will use the schema generated for the `authors` collection:
+
+```json
+{
+  "yaml.schemas": {
+    "./.astro/collections/authors.schema.json": ["/src/content/authors/*.yml"]
+  }
+}
+```
+
+See [“Associating schemas”](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml#associating-schemas) in the Red Hat YAML extension documentation for more details.
+
 ## When to create a collection
 
 You can [create a collection](#defining-collections) any time you have a group of related data or content that shares a common structure.

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

@@ -8,12 +8,51 @@ i18nReady: true
 stub: true
 ---
 
+import { Steps } from '@astrojs/starlight/components';
+
 [Railway](https://railway.com) is a deployment platform built to simplify your infrastructure stack from servers to observability with a single, scalable platform.
 
+This guide is for deploying an Astro static site to Railway using either the web interface or Railway CLI tool.
+
+:::tip
+To deploy an Astro site with on-demand rendering (SSR) using the Node adapter, you can follow [Railway's guide to deploying an Astro site](https://docs.railway.com/guides/astro).
+:::
+
+## Project Configuration
+
+Railway's default build system, [Railpack](https://docs.railway.com/reference/railpack), automatically builds your Astro project as a static site.
+
+## Deploy via the web interface
+
+<Steps>
+  1. Create a [Railway account](https://railway.com/dashboard) and sign in.
+
+  2. From the Railway dashboard, create a new [project](https://docs.railway.com/guides/projects).
+  
+  3. Select the option to deploy from a GitHub repository, and select your Astro project.
+  
+  4. Generate or add a custom domain from your project's [network settings](https://docs.railway.com/guides/public-networking#railway-provided-domain).
+</Steps>
+
+## Deploy via Railway CLI
+
+<Steps>
+  1. [Install](https://docs.railway.com/guides/cli#installing-the-cli) the Railway CLI tool.
+
+  2. Login with the command `railway login`.
+  
+  3. From within your Astro project, run `railway init` and choose a workspace and project name.
+  
+  4. Run `railway up` to deploy your project on Railway.
+  
+  5. Run `railway domain` to generate a Railway provided service domain.
+</Steps>
+
+
 ## Official Resources 
 
 [Railway guide to deploying an Astro app](https://docs.railway.com/guides/astro)
 
 ## Community Resources 
 
-[How to host an Astro site on Railway](https://jacksmith.xyz/blog/how-to-host-astro-site-on-railway)
+[How to host an Astro site on Railway](https://jacksmith.xyz/blog/how-to-host-astro-site-on-railway)

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

@@ -9,6 +9,7 @@ category: renderer
 i18nReady: true
 ---
 import PackageManagerTabs from '~/components/tabs/PackageManagerTabs.astro'
+import Since from '~/components/Since.astro';
 
 This **[Astro integration][astro-integration]** enables rendering and client-side hydration for your [React](https://react.dev/) components.
 
@@ -114,6 +115,79 @@ To use your first React component in Astro, head to our [UI framework documentat
 * 💧 client-side hydration options, and
 * 🤝 opportunities to mix and nest frameworks together
 
+## Integrate Actions with `useActionState()` (experimental)
+
+The `@astrojs/react` integration provides two experimental functions for use with [Astro Actions][astro-actions]: `experimental_withState()` and `experimental_getActionState()`.
+
+These are used with [React's useActionState() hook](https://react.dev/reference/react/useActionState) to read and update client-side state when triggering actions during form submission.
+
+### `experimental_withState()`
+
+<p>
+
+**Type:** `(action: FormFn<T>) => (state: T, formData: FormData) => FormFn<T>`<br />
+<Since v="4.3.2" />
+</p>
+
+You can pass `experimental_withState()` and the action you want to trigger to React's `useActionState()` hook as the form action function. The example below passes a `like` action to increase a counter along with an initial state of `0` likes.
+
+```jsx title="Like.tsx" ins={2,7} "useActionState"
+import { actions } from 'astro:actions';
+import { experimental_withState } from '@astrojs/react/actions';
+import { useActionState } from "react";
+
+export function Like({ postId }: { postId: string }) {
+  const [state, action, pending] = useActionState(
+    experimental_withState(actions.like),
+    { data: 0, error: undefined }, // initial likes and errors
+  );
+
+  return (
+    <form action={action}>
+      <input type="hidden" name="postId" value={postId} />
+      <button disabled={pending}>{state.data} ❤️</button>
+    </form>
+  );
+}
+```
+
+The `experimental_withState()` function will match the action's types with React's expectations and preserve metadata used for progressive enhancement, allowing it to work even when JavaScript is disabled on the user's device.
+
+### `experimental_getActionState()`
+
+<p>
+
+**Type:** `(context: ActionAPIContext) => Promise<T>`<br />
+<Since v="4.3.2" />
+</p>
+
+You can access the state stored by `useActionState()` on the server in your action `handler` with `experimental_getActionState()`. It accepts the [Astro API context](/en/reference/api-reference/#the-context-object), and optionally, you can apply a type to the result. 
+
+The example below gets the current value of likes from a counter, typed as a number, in order to create an incrementing `like` action:
+
+```ts title="actions.ts" ins={3,11}
+import { defineAction, type SafeResult } from 'astro:actions';
+import { z } from 'astro:schema';
+import { experimental_getActionState } from '@astrojs/react/actions';
+
+export const server = {
+  like: defineAction({
+    input: z.object({
+      postId: z.string(),
+    }),
+    handler: async ({ postId }, ctx) => {
+      const { data: currentLikes = 0, error } = await experimental_getActionState<SafeResult<any, number>>(ctx);
+      
+      // handle errors
+      if (error) throw error;
+
+      // write to database
+      return currentLikes + 1;
+    },
+  })
+};
+```
+
 ## Options
 
 ### Combining multiple JSX frameworks
@@ -201,11 +275,13 @@ export default defineConfig({
   integrations: [
     react({
       experimentalDisableStreaming: true,
-    }),
-  ],
+    })
+  ]
 });
 ```
 
 [astro-integration]: /en/guides/integrations-guide/
 
 [astro-ui-frameworks]: /en/guides/framework-components/#using-framework-components
+
+[astro-actions]: /en/guides/actions/

src/content/docs/es/basics/astro-pages.mdx

@@ -104,7 +104,7 @@ Esto generará una página `404.html` que la mayoría de los [servicios de despl
 
 ## Página de error 500 personalizada
 
-Para que una página de error 500 personalizada se muestre para las páginas que se [renderizan bajo demanda](/es/guides/on-demand-rendering/), crea el archivo `src/pages/500.astro`. Esta página personalizada no está disponible para las páginas prerenderizadas y no puede ser prerenderizada.
+Para que una página de error 500 personalizada se muestre para las páginas que se [renderizan bajo demanda](/es/guides/on-demand-rendering/), crea el archivo `src/pages/500.astro`. Esta página personalizada no está disponible para las páginas prerenderizadas.
 
 Si se produce un error al renderizar esta página, se mostrará la página de error 500 predeterminada de tu host a tu visitante.
 

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

@@ -77,7 +77,7 @@ Las instrucciones de instalación, integración del editor e información adicio
 
 ### Prettier
 
-[Prettier](https://prettier.io/) es un formateador popular para JavaScript, HTML, CSS y más. Si estás usando la [extensión de VS Code de Astro](https://marketplace.visualstudio.com/items?itemName=astro-build.astro-vscode) o [el servidor de lenguaje de Astro dentro de otro editor](#otros-editores-de-código), el formateo de código con Prettier está incluido.
+[Prettier](https://prettier.io/) es un formateador popular para JavaScript, HTML, CSS y más. Si estás usando la [extensión de VS Code de Astro](https://marketplace.visualstudio.com/items?itemName=astro-build.astro-vscode), el formateo de código con Prettier está incluido.
 
 Para dar soporte al formateo de archivos `.astro` fuera del editor (por ejemplo, CLI) o dentro de editores que no soportan nuestras herramientas de editor, instala [el plugin oficial de Prettier de Astro](https://github.com/withastro/prettier-plugin-astro).
 

src/content/docs/fr/guides/authentication.mdx

@@ -25,7 +25,7 @@ Auth.js est une solution d'authentification indépendante du framework. Un adapt
 
 ### Installation
 
-Utilisez la commande `astro add` de votre gestionnaire de paquets préféré pour ajouter l'intégration `auth-astro`.
+Utilisez la commande `astro add` de votre gestionnaire de paquets préféré pour ajouter l'intégration `auth-astro` à un projet Astro configuré avec un [adaptateur de serveur](/fr/guides/on-demand-rendering/#adaptateurs-de-serveur) pour le rendu à la demande.
 
 <PackageManagerTabs>
   <Fragment slot="npm">
@@ -69,12 +69,13 @@ Pour installer `auth-astro` manuellement, installez le paquet requis pour votre
 
 Ensuite, appliquez l'intégration à votre fichier `astro.config.*` en utilisant la propriété `integrations` :
 
-```ts title="astro.config.mjs" ins={2,6}
+```ts title="astro.config.mjs" ins={2,7}
 import { defineConfig } from 'astro/config';
 import auth from 'auth-astro';
 
 export default defineConfig({
   // ...
+  adapter: netlify(),
   integrations: [auth()],
 });
 ```

src/content/docs/fr/guides/integrations-guide/sitemap.mdx

@@ -516,6 +516,38 @@ export default defineConfig({
 
 La configuration donnée générera des fichiers de sitemap aux adresses `https://example.com/sitemap-astronomie-0.xml` et `https://example.com/sitemap-astronomie-index.xml`.
 
+### `namespaces`
+
+<p>
+
+**Type :** `{ news?: boolean; xhtml?: boolean; image?: boolean; video?: boolean; }` <br />
+**Par défaut :** `{ news: true, xhtml: true, image: true, video: true }` <br />
+<Since v="3.6.0" pkg="@astrojs/sitemap" />
+</p>
+
+Un objet d’espaces de noms XML à exclure du sitemap généré.
+
+L'exclusion des espaces de noms inutilisés peut aider à créer des sitemaps plus ciblés, plus rapides à analyser par les moteurs de recherche et utilisant moins de bande passante. Par exemple, si votre site ne propose pas des actualités, des vidéos ou de contenu multilingue, vous pouvez exclure ces espaces de noms pour réduire la surcharge XML.
+
+Par défaut, tous les espaces de noms configurables (`news`, `xhtml`, `image` et `video`) sont inclus dans le sitemap généré en XML. Pour exclure un ou plusieurs de ces espaces de noms de la génération de votre sitemap, ajoutez un objet de configuration `namespaces` et définissez les options individuelles sur `false`.
+
+```js title="astro.config.mjs" ins={8-11}
+import { defineConfig } from 'astro/config';
+import sitemap from '@astrojs/sitemap';
+
+export default defineConfig({
+  site: 'https://example.com',
+  integrations: [
+    sitemap({
+      namespaces: {
+        news: false,
+        xhtml: false, 
+      }
+    })
+  ]
+});
+```
+
 ## Exemples
 
 * Le site officiel d'Astro utilise Astro Sitemap pour générer [son plan du site](https://astro.build/sitemap-index.xml).

src/content/docs/ko/guides/astro-db.mdx

@@ -232,10 +232,6 @@ Astro DB를 사용하면 로컬 및 원격 데이터베이스에 모두 연결
 
 호스팅된 원격 데이터베이스에 연결하려면 `--remote` 플래그를 사용합니다. 이 플래그를 사용하면 원격 데이터베이스에 대한 읽기 및 쓰기 액세스가 모두 가능하므로 프로덕션 환경에서 [사용자 데이터를 허용 및 유지](#insert)할 수 있습니다.
 
-:::note
-일반적으로 정적 또는 서버 렌더링 모드를 사용하는 모든 배포 플랫폼에서 원격 연결이 가능하지만, 현재 몇 가지 제한 사항이 있습니다. Cloudflare 및 Deno와 같은 Node 기반이 아닌 런타임은 현재 libSQL을 사용할 때 서버 렌더링 경로에서 DB를 지원하지 않습니다. 이러한 플랫폼에 대한 지원은 향후 구현될 예정입니다.
-:::
-
 `--remote` 플래그를 사용하도록 빌드 명령을 구성합니다:
 
 ```json title="package.json" "--remote"
@@ -260,7 +256,7 @@ astro dev --remote
 개발 모드에서 `--remote`를 사용할 때는 주의하세요. 이렇게 하면 라이브 프로덕션 데이터베이스에 연결되며 모든 변경 사항 (삽입, 업데이트, 삭제)이 유지됩니다.
 :::
 
-`--remote` 플래그는 로컬 빌드와 서버에서 모두 원격 DB에 대한 연결을 사용합니다. 로컬 개발 환경과 배포 플랫폼 모두에서 필요한 환경 변수를 설정했는지 확인하세요.
+`--remote` 플래그는 로컬 빌드와 서버에서 모두 원격 DB에 대한 연결을 사용합니다. 로컬 개발 환경과 배포 플랫폼 모두에서 필요한 환경 변수를 설정했는지 확인하세요. 또한 Cloudflare Workers나 Deno와 같은 Node.js가 아닌 런타임 환경에서는 [웹 모드를 구성](/ko/guides/integrations-guide/db/#mode)해야 할 수도 있습니다.
 
 Astro DB 프로젝트를 배포할 때, 배포 플랫폼의 빌드 명령이 `package.json`에 구성된 `--remote` 플래그를 활용하도록 `npm run build` (또는 패키지 관리자에 상응하는 명령어)로 설정되어 있는지 확인하세요.
 

src/content/docs/ko/guides/integrations-guide/db.mdx

@@ -11,6 +11,7 @@ i18nReady: true
 import { FileTree } from '@astrojs/starlight/components';
 import PackageManagerTabs from '~/components/tabs/PackageManagerTabs.astro';
 import ReadMore from '~/components/ReadMore.astro';
+import Since from '~/components/Since.astro';
 
 Astro DB는 Astro 생태계를 위해 설계된 완전 관리형 SQL 데이터베이스입니다. Astro에서 로컬로 개발하고 모든 [libSQL 호환 데이터베이스](/ko/guides/astro-db/)에 배포하세요.
 
@@ -92,6 +93,38 @@ export default defineDb({
 })
 ```
 
+## 구성
+
+### `mode`
+
+<p>
+
+**타입:** `'node' | 'web'`<br />
+**기본값:** `'node'`<br />
+<Since v="0.18.0" pkg="@astrojs/db" />
+</p>
+
+프로덕션 환경에서 데이터베이스에 연결할 때 사용할 드라이버를 구성합니다.
+
+기본적으로 Astro DB는 프로덕션 배포에 Node.js 기반 libSQL 드라이버를 사용합니다. Node.js 런타임을 사용하는 대부분의 Astro 호스팅 또는 자체 호스팅 웹사이트에는 `node` 드라이버 모드로 충분합니다. 이를 통해 `memory:`, `file:`, `ws:`, `wss:`, `libsql`, `http`, `https` 등 여러 프로토콜을 통해 데이터베이스에 연결할 수 있으며, [임베디드 레플리카](/ko/guides/astro-db/#syncurl)와 같은 고급 기능도 사용할 수 있습니다.
+
+Cloudflare Workers나 Deno와 같은 Node.js가 아닌 런타임의 서버리스 환경에 배포할 경우, 웹 기반 libSQL 드라이버를 사용할 수 있습니다. `web` 모드를 사용하여 배포할 경우, `libsql`, `http`, `https`를 통해 웹 기반 연결을 설정할 수 있습니다.
+
+Node.js 환경이 아닌 경우 웹 libSQL 드라이버 모드를 사용하려면 어댑터 구성에서 `mode` 속성을 설정해야 합니다.
+
+```ts title="astro.config.mjs" ins={7}
+import { defineConfig } from 'astro/config';
+import db from '@astrojs/db';
+
+export default defineConfig({
+  integrations: [
+   db({
+     mode: 'web'
+   })
+  ]
+});
+```
+
 ## 테이블 구성 참조
 
 ### `columns`