withastro · sarah11918 · Dec 2, 2024 · Nov 19, 2024 · Nov 20, 2024 · Nov 21, 2024
diff --git a/astro.sidebar.ts b/astro.sidebar.ts
@@ -92,11 +92,12 @@ export const sidebar = [
 	group('reference', {
 		items: [
 			group('reference.syntax', {
-				items: ['basics/astro-syntax', 'reference/directives-reference'],
+				items: ['reference/astro-syntax', 'reference/directives-reference'],
 			}),
 			'reference/configuration-reference',
 			'reference/cli-reference',
 			'guides/imports',
+			'reference/routing-reference',
 			group('reference.runtime', {
 				items: [
 					'reference/api-reference',

diff --git a/public/_redirects b/public/_redirects
@@ -31,10 +31,11 @@
 /:lang/guides/content/                               /:lang/guides/markdown-content/
 /:lang/community-resources/talks/                    /:lang/recipes/
 /:lang/community-resources/content/                  /:lang/recipes/
-/:lang:/reference/components-reference/              /:lang:/guides/syntax-highlighting/
-/:lang:/tutorials/add-content-collections/           /:lang:/tutorial/6-islands/4/
-/:lang:/tutorials/add-view-transitions/              /:lang:/guides/view-transitions/
+/:lang/reference/components-reference/               /:lang/guides/syntax-highlighting/
+/:lang/tutorials/add-content-collections/            /:lang/tutorial/6-islands/4/
+/:lang/tutorials/add-view-transitions/               /:lang/guides/view-transitions/
 /:lang/guides/rss/                                   /:lang/recipes/rss/
+/:lang/basics/astro-syntax/                          /:lang/reference/astro-syntax/
 
 # Very old docs site redirects
 # Once upon a time these URLs existed, so we try to keep them meaning something.

diff --git a/src/content/docs/ar/basics/astro-components.mdx b/src/content/docs/ar/basics/astro-components.mdx
@@ -63,7 +63,7 @@ const data = await fetch('SOME_SECRET_API_URL/users').then(r => r.json());
 
 اذا قمت بكتابة HTML العادي هنا، فسيقوم المكوّن الخاص بك بتصيير ذلك الـ HTML في أي صفحة أسترو يتم استيرادها واستخدامها.
 
-ومع ذلك، يدعم [ بناء قالب المكوّن لأسترو](/ar/basics/astro-syntax/) كذلك **تعابير جافاسكربت**، وسوم [`<style>`](/ar/guides/styling/#styling-in-astro) و[`<script>`](/ar/guides/client-side-scripts/#using-script-in-astro) لأسترو والمكوّنات المستوردة و[توجيهات أسترو الخاصة](/ar/reference/directives-reference/). البيانات والقيم المعرّفة في البرنامج النصي للمكوّن يمكن إستخدامها في قالب المكوّن لإنتاج HTML مُنشأ ديناميكيًا.
+ومع ذلك، يدعم [ بناء قالب المكوّن لأسترو](/ar/reference/astro-syntax/) كذلك **تعابير جافاسكربت**، وسوم [`<style>`](/ar/guides/styling/#styling-in-astro) و[`<script>`](/ar/guides/client-side-scripts/#using-script-in-astro) لأسترو والمكوّنات المستوردة و[توجيهات أسترو الخاصة](/ar/reference/directives-reference/). البيانات والقيم المعرّفة في البرنامج النصي للمكوّن يمكن إستخدامها في قالب المكوّن لإنتاج HTML مُنشأ ديناميكيًا.
 
 ```astro title="src/components/MyFavoritePokemon.astro"
 ---

diff --git a/src/content/docs/ar/getting-started.mdx b/src/content/docs/ar/getting-started.mdx
@@ -52,7 +52,7 @@ import Discord from '~/components/Landing/Discord.astro'
     - [ميزات أسترو الرئيسية](/ar/concepts/why-astro/)
     - [معمارية جزر أسترو](/ar/concepts/islands/)
     - [مكونات أسترو](/ar/basics/astro-components/)
-    - [بناء جملة قالب أسترو](/ar/basics/astro-syntax/)
+    - [بناء جملة قالب أسترو](/ar/reference/astro-syntax/)
   </ListCard>
 
   <ListCard title="امتداد" icon="puzzle">

diff --git a/src/content/docs/de/basics/astro-components.mdx b/src/content/docs/de/basics/astro-components.mdx
@@ -63,7 +63,7 @@ Unterhalb des Komponentenskripts befindet sich die Komponentenvorlage. Sie besti
 
 Wenn du hier einfaches HTML schreibst, wird deine Komponente dieses HTML auf jeder Astro-Seite rendern, auf der sie importiert und verwendet wird.
 
-Die [Syntax der Astro-Komponentenvorlage](/de/basics/astro-syntax/) unterstützt jedoch auch **JavaScript-Ausdrücke**, Astro-[`<style>`](/de/guides/styling/#styles-stile-in-astro) und [`<script>`](/de/guides/client-side-scripts/#verwendung-von-script-in-astro)-Tags, **importierte Komponenten** und [**spezielle Astro-Direktiven**](/de/reference/directives-reference/). Daten und Werte, die im Komponentenskript definiert werden, können in der Komponentenvorlage verwendet werden, um dynamisch erstelltes HTML zu erzeugen.
+Die [Syntax der Astro-Komponentenvorlage](/de/reference/astro-syntax/) unterstützt jedoch auch **JavaScript-Ausdrücke**, Astro-[`<style>`](/de/guides/styling/#styles-stile-in-astro) und [`<script>`](/de/guides/client-side-scripts/#verwendung-von-script-in-astro)-Tags, **importierte Komponenten** und [**spezielle Astro-Direktiven**](/de/reference/directives-reference/). Daten und Werte, die im Komponentenskript definiert werden, können in der Komponentenvorlage verwendet werden, um dynamisch erstelltes HTML zu erzeugen.
 
 ```astro title="src/components/MeineLieblingspokemon.astro"
 ---
@@ -251,7 +251,7 @@ import Wrapper from '../components/Wrapper.astro';
 Verwende ein `slot="mein-slot"`-Attribut auf dem untergeordneten Element, das du an einen passenden `<slot name="mein-slot" />`-Platzhalter in deiner Komponente weiterleiten willst.
 :::
 
-Um mehrere HTML-Elemente ohne ein umschließendes `<div>` in den `<slot/>`-Platzhalter einer Komponente zu übergeben, verwende das `slot=""`-Attribut auf [Astros <Fragment/>-Komponente](/de/basics/astro-syntax/#fragmente):
+Um mehrere HTML-Elemente ohne ein umschließendes `<div>` in den `<slot/>`-Platzhalter einer Komponente zu übergeben, verwende das `slot=""`-Attribut auf [Astros <Fragment/>-Komponente](/de/reference/astro-syntax/#fragmente):
 
 
 ```astro title="src/components/CustomTable.astro" '<slot name="header" />' '<slot name="body" />'

diff --git a/src/content/docs/de/getting-started.mdx b/src/content/docs/de/getting-started.mdx
@@ -52,7 +52,7 @@ import Discord from '~/components/Landing/Discord.astro'
     - [Astros Hauptmerkmale](/de/concepts/why-astro/)
     - [Insel-Architektur](/de/concepts/islands/)
     - [Astro Komponenten](/de/basics/astro-components/)
-    - [Die Astro Vorlagen-Syntax](/de/basics/astro-syntax/)
+    - [Die Astro Vorlagen-Syntax](/de/reference/astro-syntax/)
   </ListCard>
 
   <ListCard title="Erweitere" icon="puzzle">

diff --git a/src/content/docs/de/guides/migrate-to-astro/from-create-react-app.mdx b/src/content/docs/de/guides/migrate-to-astro/from-create-react-app.mdx
@@ -33,7 +33,7 @@ Hier sind ein paar grundlegende Konzepte und Migrations&shy;strategien, die dir
 
 ## Wesentliche Gemeinsamkeiten zwischen CRA und Astro
 
-- Die [Syntax von `.astro`-Dateien ist ähnlich zu JSX](/de/basics/astro-syntax/#unterschiede-zwischen-astro-und-jsx). Astro zu schreiben sollte sich also gewohnt anfühlen.
+- Die [Syntax von `.astro`-Dateien ist ähnlich zu JSX](/de/reference/astro-syntax/#unterschiede-zwischen-astro-und-jsx). Astro zu schreiben sollte sich also gewohnt anfühlen.
 
 - Astro verwendet dateienbasierts Routing, und [erlaubt spezielle Dateinamen, um dynamische Routen zu erstellen](/de/guides/routing/#dynamische-routen).
 
@@ -266,7 +266,7 @@ Hier sind ein paar Tipps für das Umwandeln von CRA-`.js`-Komponenten in `.astro
 
 2. Tausche jeden [CRA oder JSX Syntax gegen Astro](#referenz-wandle-cra-syntax-in-astro-um) oder gegen HTML-Web-Standards. Damit ist zum Beispiel `{children}` oder `className` gemeint.
 
-3. Verschiebe sämtliches JavaScript, inklusive `import`-Statements, in einen ["Code-Zaun" (`---`)](/de/basics/astro-components/#das-komponentenskript). Beachte: JavaScript, welches für das [bedingte Rendern von Inhalten](/de/basics/astro-syntax/#dynamisches-html) benötigt wird, wird oftmals in der HTML-Vorlage direkt in Astro geschrieben.
+3. Verschiebe sämtliches JavaScript, inklusive `import`-Statements, in einen ["Code-Zaun" (`---`)](/de/basics/astro-components/#das-komponentenskript). Beachte: JavaScript, welches für das [bedingte Rendern von Inhalten](/de/reference/astro-syntax/#dynamisches-html) benötigt wird, wird oftmals in der HTML-Vorlage direkt in Astro geschrieben.
 
 4. Verwende [`Astro.props`](/de/reference/api-reference/#astroprops), um auf die Komponenten&shy;attribute, die zuvor deiner CRA-Komponenten&shy;funktionen weitergegeben worden sind, zuzugreifen.
 

diff --git a/src/content/docs/de/guides/troubleshooting.mdx b/src/content/docs/de/guides/troubleshooting.mdx
@@ -65,7 +65,7 @@ Dann überprüfe deine Importanweisung:
 
 - Verweist dein Import auf den falschen Ort? (Überprüfe deinen Importpfad.)
 
-- Hat dein Import den gleichen Namen wie die importierte Komponente? (Überprüfe deinen Komponentennamen und dass er der [`.astro`-Syntax folgt](/de/basics/astro-syntax/#unterschiede-zwischen-astro-und-jsx).)
+- Hat dein Import den gleichen Namen wie die importierte Komponente? (Überprüfe deinen Komponentennamen und dass er der [`.astro`-Syntax folgt](/de/reference/astro-syntax/#unterschiede-zwischen-astro-und-jsx).)
 
 - Hast du die Erweiterung in den Import aufgenommen? (Überprüfe, ob deine importierte Datei eine Erweiterung enthält, z.B. `.astro`, `.md`, `.vue`, `.svelte`. Hinweis: Dateierweiterungen sind nur für `.js(x)` und `.ts(x)` Dateien **nicht** erforderlich.)
 
@@ -138,7 +138,7 @@ In Astro funktioniert der `<head>`-Tag wie jeder andere HTML-Tag: Er wird nicht
 
 ### Ein unerwartetes `<script>`- oder `<style>`-Tag ist enthalten
 
-Es kann vorkommen, dass die `<script>`- oder `<style>`-Tags einer importierten Komponente in deinem HTML-Quelltext enthalten sind, auch wenn die Komponente in der endgültigen Ausgabe nicht erscheint. Dies ist zum Beispiel der Fall bei [bedingt gerenderten](/de/basics/astro-syntax/#dynamisches-html) Komponenten, die nicht angezeigt werden.
+Es kann vorkommen, dass die `<script>`- oder `<style>`-Tags einer importierten Komponente in deinem HTML-Quelltext enthalten sind, auch wenn die Komponente in der endgültigen Ausgabe nicht erscheint. Dies ist zum Beispiel der Fall bei [bedingt gerenderten](/de/reference/astro-syntax/#dynamisches-html) Komponenten, die nicht angezeigt werden.
 
 Der Build-Prozess von Astro arbeitet mit dem Modul-Graph: Sobald eine Komponente in der Vorlage enthalten ist, werden ihre `<script>`- und `<style>`-Tags verarbeitet, optimiert und gebündelt, unabhängig davon, ob sie in der endgültigen Ausgabe erscheint oder nicht. Dies gilt nicht für Skripte, wenn die Direktive "is:inline" angewendet wird.
 

diff --git a/src/content/docs/de/basics/astro-syntax.mdx → ...ontent/docs/de/reference/astro-syntax.mdx b/src/content/docs/de/basics/astro-syntax.mdx → ...ontent/docs/de/reference/astro-syntax.mdx
diff --git a/src/content/docs/en/basics/astro-components.mdx b/src/content/docs/en/basics/astro-components.mdx
@@ -4,7 +4,15 @@ description: An introduction to Astro components.
 i18nReady: true
 ---
 
-**Astro components** are the basic building blocks of any Astro project. They are HTML-only templating components with no client-side runtime. You can spot an Astro component by its file extension: `.astro`.
+import ReadMore from '~/components/ReadMore.astro';
+
+**Astro components** are the basic building blocks of any Astro project. They are HTML-only templating components with no client-side runtime and use the `.astro` file extension.
+
+:::note
+If you know HTML, you already know enough to write your first Astro component.
+
+<ReadMore>Learn more in the [Astro syntax reference](/en/reference/astro-syntax/).</ReadMore>
+:::
 
 Astro components are extremely flexible. An Astro component can be as small as a snippet of HTML, like a collection of common `<meta>` tags that make SEO easy to work with. Components can be reusable UI elements, like a header or a profile card. Astro components can even contain an entire page layout or, when located in the special `src/pages/` folder, be an entire page itself.
 
@@ -54,8 +62,10 @@ const data = await fetch('SOME_SECRET_API_URL/users').then(r => r.json());
 
 The code fence is designed to guarantee that the JavaScript that you write in it is "fenced in." It won't escape into your frontend application, or fall into your user's hands. You can safely write code here that is expensive or sensitive (like a call to your private database) without worrying about it ever ending up in your user's browser.
 
-:::tip
-You can even write TypeScript in your component script!
+:::note
+The Astro component script is TypeScript, which allows you to add additional syntax to JavaScript for editor tooling, and error checking.
+
+<ReadMore>Read more about Astro's [built-in TypeScript support](/en/guides/typescript/).</ReadMore>
 :::
 
 ### The Component Template
@@ -64,7 +74,7 @@ The component template is below the code fence and determines the HTML output of
 
 If you write plain HTML here, your component will render that HTML in any Astro page it is imported and used.
 
-However, [Astro's component template syntax](/en/basics/astro-syntax/) also supports **JavaScript expressions**, Astro [`<style>`](/en/guides/styling/#styling-in-astro) and [`<script>`](/en/guides/client-side-scripts/#using-script-in-astro) tags, **imported components**, and [**special Astro directives**](/en/reference/directives-reference/). Data and values defined in the component script can be used in the component template to produce dynamically-created HTML.
+However, [Astro's component template syntax](/en/reference/astro-syntax/) also supports **JavaScript expressions**, Astro [`<style>`](/en/guides/styling/#styling-in-astro) and [`<script>`](/en/guides/client-side-scripts/#using-script-in-astro) tags, **imported components**, and [**special Astro directives**](/en/reference/directives-reference/). Data and values defined in the component script can be used in the component template to produce dynamically-created HTML.
 
 ```astro title="src/components/MyFavoritePokemon.astro"
 ---
@@ -259,7 +269,7 @@ import Wrapper from '../components/Wrapper.astro';
 Use a `slot="my-slot"` attribute on the child element that you want to pass through to a matching `<slot name="my-slot" />` placeholder in your component.
 :::
 
-To pass multiple HTML elements into a component's `<slot/>` placeholder without a wrapping `<div>`, use the `slot=""` attribute on [Astro's `<Fragment/>` component](/en/basics/astro-syntax/#fragments):
+To pass multiple HTML elements into a component's `<slot/>` placeholder without a wrapping `<div>`, use the `slot=""` attribute on [Astro's `<Fragment/>` component](/en/reference/astro-syntax/#fragments):
 
 ```astro title="src/components/CustomTable.astro" "<slot name="header"/>" "<slot name="body"/>"
 ---
@@ -393,6 +403,4 @@ A [`<slot />` element](/en/basics/astro-components/#slots) inside an HTML compon
 
 ## Next Steps
 
-import ReadMore from '~/components/ReadMore.astro';
-
 <ReadMore>Read more about using [UI framework components](/en/guides/framework-components/) in your Astro project.</ReadMore>
diff --git a/src/content/docs/en/basics/astro-pages.mdx b/src/content/docs/en/basics/astro-pages.mdx
@@ -152,9 +152,7 @@ However, because they are located in the special `src/pages/` directory, the gen
 
 Partials, when combined with a rendering library, provide an alternative to [Astro islands](/en/concepts/islands/) and [`<script>` tags](/en/guides/client-side-scripts/) for building dynamic content in Astro.
 
-Page files that can export a value (e.g. `.astro` , `.mdx`) can be marked as partials.
-
-Configure a file within the `src/pages/` directory to be a partial by adding the following export:
+Page files that can export a value for [`partial`](/en/reference/routing-reference/#partial) (e.g. `.astro` and `.mdx`, but not `.md`) can be marked as partials.
 
 ```astro title="src/pages/partial.astro" ins={2}
 ---
@@ -164,11 +162,6 @@ export const partial = true;
 <li>I'm a partial!</li>
 ```
 
-The `export const partial` must be identifiable statically. It can have the value of:
-
-- The boolean __`true`__.
-- An environment variable using import.meta.env such as `import.meta.env.USE_PARTIALS`.
-
 ### Using with a library
 
  Partials are used to dynamically update a section of a page using a library such as [htmx](https://htmx.org/).

diff --git a/src/content/docs/en/getting-started.mdx b/src/content/docs/en/getting-started.mdx
@@ -50,7 +50,7 @@ import Discord from '~/components/Landing/Discord.astro'
     - [Astro's main features](/en/concepts/why-astro/)
     - [Islands architecture](/en/concepts/islands/)
     - [Astro components](/en/basics/astro-components/)
-    - [The Astro template syntax](/en/basics/astro-syntax/)
+    - [The Astro template syntax](/en/reference/astro-syntax/)
   </ListCard>
 
   <ListCard title="Extend" icon="puzzle">

diff --git a/src/content/docs/en/guides/actions.mdx b/src/content/docs/en/guides/actions.mdx
@@ -403,7 +403,7 @@ Pages must be on-demand rendered when calling actions using a form action. [Ensu
 
 You can enable zero-JS form submissions with standard attributes on any `<form>` element.  Form submissions without client-side JavaScript may be useful both as a fallback for when JavaScript fails to load, or if you prefer to handle forms entirely from the server.
 
-Calling [Astro.getActionResult()](/en/reference/api-reference/#astrogetactionresult) on the server returns the result of your form submission (`data` or `error`), and can be used to dynamically redirect, handle form errors, update the UI, and more.
+Calling [Astro.getActionResult()](/en/reference/api-reference/#getactionresult) on the server returns the result of your form submission (`data` or `error`), and can be used to dynamically redirect, handle form errors, update the UI, and more.
 
 To call an action from an HTML form, add `method="POST"` to your `<form>`, then set the form's `action` attribute using your action, for example `action={actions.logout}`. This will set the `action` attribute to use a query string that is handled by the server automatically.
 

diff --git a/src/content/docs/en/guides/cms/builderio.mdx b/src/content/docs/en/guides/cms/builderio.mdx
@@ -261,7 +261,7 @@ Create the page `src/pages/posts/[slug].astro` that will [dynamically generate a
 </FileTree>
 
 This file must contain:
-- A [`getStaticPaths()`](/en/reference/api-reference/#getstaticpaths) function to fetch `slug` information from Builder and create a static route for each blog post.
+- A [`getStaticPaths()`](/en/reference/routing-reference/#getstaticpaths) function to fetch `slug` information from Builder and create a static route for each blog post.
 - A `fetch()` to the Builder API using the `slug` identifier to return post content and metadata (e.g. a `title`).
 - A `<Fragment />` in the template to render the post content as HTML.
 
@@ -322,7 +322,7 @@ const { html: postHTML } = await fetch(
 ```
 
 :::note
-The variables `builderModel` and `builderAPIpublicKey` need to be created twice, since [`getStaticPaths()` runs in its own isolated scope](/en/reference/api-reference/#getstaticpaths).
+The variables `builderModel` and `builderAPIpublicKey` need to be created twice, since [`getStaticPaths()` runs in its own isolated scope](/en/reference/routing-reference/#getstaticpaths).
 :::
 
 Now when you click on a link on your index route, you will be taken to the individual blog post page.

diff --git a/src/content/docs/en/guides/cms/contentful.mdx b/src/content/docs/en/guides/cms/contentful.mdx
@@ -431,7 +431,7 @@ Navigate to http://localhost:4321/ and click on one of your posts to make sure y
 
 If you've [opted in to SSR mode](/en/guides/on-demand-rendering/), you will use a dynamic route that uses a `slug` parameter to fetch the data from Contentful.
 
-Create a `[slug].astro` page in `src/pages/posts`. Use [`Astro.params`](/en/reference/api-reference/#astroparams) to get the slug from the URL, then pass that to `getEntries`: 
+Create a `[slug].astro` page in `src/pages/posts`. Use [`Astro.params`](/en/reference/api-reference/#params) to get the slug from the URL, then pass that to `getEntries`: 
 
 ```astro title="src/pages/posts/[slug].astro"
 ---

diff --git a/src/content/docs/en/guides/cms/strapi.mdx b/src/content/docs/en/guides/cms/strapi.mdx
@@ -243,7 +243,7 @@ Create the file `src/pages/blog/[slug].astro` to [dynamically generate a page](/
 
 #### Static site generation
 
-In Astro's default static mode (SSG), use [`getStaticPaths()`](/en/reference/api-reference/#getstaticpaths) to fetch your list of articles from Strapi.
+In Astro's default static mode (SSG), use [`getStaticPaths()`](/en/reference/routing-reference/#getstaticpaths) to fetch your list of articles from Strapi.
 
 ```astro title="src/pages/blog/[slug].astro
 ---

diff --git a/src/content/docs/en/guides/content-collections.mdx b/src/content/docs/en/guides/content-collections.mdx
@@ -504,7 +504,7 @@ The exact method for generating routes will depend on whether your pages are pre
 
 ### Building for static output (default)
 
-If you are building a static website (Astro's default behavior), use the [`getStaticPaths()`](/en/reference/api-reference/#getstaticpaths) function to create multiple pages from a single page component (e.g. `src/pages/[slug]`) during your build.
+If you are building a static website (Astro's default behavior), use the [`getStaticPaths()`](/en/reference/routing-reference/#getstaticpaths) function to create multiple pages from a single page component (e.g. `src/pages/[slug]`) during your build.
 
 Call `getCollection()` inside of `getStaticPaths()` to have your collection data available for building static routes. Then, create the individual URL paths using the `id` property of each content entry. Each page is passed the entire collection entry as a prop for [use in your page template](#using-content-in-astro-templates).