remove most ssr page link anchors

old-translations/de/core-concepts/endpoints.mdx

@@ -100,7 +100,7 @@ Alles, was bei den Endpunkten für statische Dateien beschrieben wurde, kann auc
 Im Gegensatz zum `static`-Modus werden allerdings im `server`-Modus deine Endpunkte erst dann erzeugt, wenn eine Anfrage für sie empfangen wird. Dies ermöglicht den Zugriff auf neue Funktionen, die zum Erstellungszeitpunkt nicht verfügbar sind, und erlaubt es dir, API-Routen zu erstellen, die auf Anfragen warten und ihren Code zur Laufzeit in einer sicheren Server-Umgebung ausführen.
 
 :::note
-Stelle sicher, dass du [SSR aktivierst](/de/guides/server-side-rendering/#ssr-in-deinem-projekt-aktivieren), bevor du diese Beispiele ausprobierst.
+Stelle sicher, dass du [SSR aktivierst](/de/guides/server-side-rendering/), bevor du diese Beispiele ausprobierst.
 :::
 
 Server-Endpunkte können auf `params` zugreifen, ohne `getStaticPaths` zu exportieren, und sie können ein [`Response`](https://developer.mozilla.org/en-US/docs/Web/API/Response)-Objekt zurückgeben, welches dir ermöglicht, Statuscodes und Header zu setzen:

old-translations/de/guides/rss.mdx

@@ -7,7 +7,7 @@ Astro unterstützt die schnelle, automatische Generierung von RSS-Feeds für Blo
 
 ## Einrichten von `@astrojs/rss`
 
-Das `@astrojs/rss`-Paket bietet Hilfsfunktionen zur Erzeugung von RSS-Feeds mithilfe von [API-Endpunkten](/de/core-concepts/astro-pages/#nicht-html-seiten). Dies ermöglicht _sowohl_ statische Feeds, die zum Erstellungszeitpunkt der Website generiert werden, als auch die On-Demand-Generierung bei Verwendung eines [SSR-Adapters](/de/guides/server-side-rendering/#ssr-in-deinem-projekt-aktivieren).
+Das `@astrojs/rss`-Paket bietet Hilfsfunktionen zur Erzeugung von RSS-Feeds mithilfe von [API-Endpunkten](/de/core-concepts/astro-pages/#nicht-html-seiten). Dies ermöglicht _sowohl_ statische Feeds, die zum Erstellungszeitpunkt der Website generiert werden, als auch die On-Demand-Generierung bei Verwendung eines [SSR-Adapters](/de/guides/server-side-rendering/).
 
 Installiere zu Beginn `@astrojs/rss` mit deinem bevorzugten Paketmanager:
 

old-translations/fr/core-concepts/endpoints.mdx

@@ -102,7 +102,7 @@ Tout ce qui est décrit dans la section des points de terminaison statiques peut
 Mais, à la différence du mode `static`, lorsque vous configurez le mode `server`, les points de terminaison seront construits à la demande. Ceci déverrouille de nouvelles fonctionnalités qui ne sont pas disponibles au moment de la compilation, et vous permet de construire des routes d'API qui écoutent les demandes et exécutent le code de manière sécurisée sur le serveur au moment de l'exécution.
 
 :::note
-Soyez sûr d'avoir [activé le SSR](/fr/guides/server-side-rendering/#activation-du-mode-ssr-dans-votre-projet) avant d'essayer ces exemples.
+Soyez sûr d'avoir [activé le SSR](/fr/guides/server-side-rendering/) avant d'essayer ces exemples.
 :::
 
 Les points de terminaison serveur peuvent accéder aux `params` sans avoir à exporter `getStaticPaths`, et ils peuvent retourner un objet [`Response`](https://developer.mozilla.org/en-US/docs/Web/API/Response), permettant d'affecter des codes de statut et des en-têtes :

old-translations/fr/guides/rss.mdx

@@ -11,7 +11,7 @@ Astro prend en charge la génération rapide et automatique de flux RSS pour les
 
 ## Mise en place d'`@astrojs/rss`
 
-Le [package `@astrojs/rss`](https://github.com/withastro/astro/tree/main/packages/astro-rss) fournit des fonctions d'aide pour la génération de flux RSS en utilisant des ["API endpoints" (ou points d'arrêt API)](/fr/core-concepts/endpoints/#points-de-terminaison-statiques). Cela permet de débloquer à la fois les builds statiques _et_ la génération à la demande lors de l'utilisation d'un [adaptateur SSR](/fr/guides/server-side-rendering/#activation-du-mode-ssr-dans-votre-projet).
+Le [package `@astrojs/rss`](https://github.com/withastro/astro/tree/main/packages/astro-rss) fournit des fonctions d'aide pour la génération de flux RSS en utilisant des ["API endpoints" (ou points d'arrêt API)](/fr/core-concepts/endpoints/#points-de-terminaison-statiques). Cela permet de débloquer à la fois les builds statiques _et_ la génération à la demande lors de l'utilisation d'un [adaptateur SSR](/fr/guides/server-side-rendering/).
 
 Pour commencer, installez `@astrojs/rss` en utilisant votre gestionnaire de Package préféré :
 

src/content/docs/de/core-concepts/endpoints.mdx

@@ -99,7 +99,7 @@ Im Gegensatz zum `static`-Modus werden die Endpunkte bei der Konfiguration des `
 <RecipeLinks slugs={["de/recipes/call-endpoints" ]}/>
 
 :::note
-Stelle sicher, dass du [SSR aktivierst](/de/guides/server-side-rendering/#ssr-in-deinem-projekt-aktivieren), bevor du diese Beispiele ausprobierst.
+Stelle sicher, dass du [SSR aktivierst](/de/guides/server-side-rendering/), bevor du diese Beispiele ausprobierst.
 :::
 
 Server-Endpunkte können auf `params` zugreifen, ohne `getStaticPaths` zu exportieren, und sie können ein [`Response`](https://developer.mozilla.org/en-US/docs/Web/API/Response)-Objekt zurückgeben, welches dir ermöglicht, Statuscodes und Header zu setzen:

src/content/docs/de/guides/deploy.mdx

@@ -77,6 +77,6 @@ Die Build-Ausgabe wird standardmäßig ins Verzeichnis `dist/` geschrieben. Dies
 :::note
 Bevor du deine Website mit aktiviertem [SSR (serverseitigem Rendern)](/de/guides/server-side-rendering/) veröffentlichst, stelle bitte Folgendes sicher:
 
-    - Du hast den [geeigneten SSR-Adapter](/de/guides/server-side-rendering/#ssr-in-deinem-projekt-aktivieren) als Projektabhängigkeit installiert.
+    - Du hast den [geeigneten SSR-Adapter](/de/guides/server-side-rendering/) als Projektabhängigkeit installiert.
     - Du hast die [Konfiguration angepasst](/de/reference/configuration-reference/#integrations) und den Adapter zu den Imports sowie dem Standard-Export deiner `astro.config.mjs`-Datei hinzugefügt.
 :::

src/content/docs/de/guides/rss.mdx

@@ -11,7 +11,7 @@ Astro unterstützt die schnelle, automatische Generierung von RSS-Feeds für Blo
 
 ## Einrichten von `@astrojs/rss`
 
-Das `@astrojs/rss`-Paket bietet Hilfsfunktionen zur Erzeugung von RSS-Feeds mithilfe von [API-Endpunkten](/de/core-concepts/astro-pages/#nicht-html-seiten). Dies ermöglicht statische Feeds _und_ die On-Demand-Generierung bei Verwendung eines [SSR-Adapters](/de/guides/server-side-rendering/#ssr-in-deinem-projekt-aktivieren).
+Das `@astrojs/rss`-Paket bietet Hilfsfunktionen zur Erzeugung von RSS-Feeds mithilfe von [API-Endpunkten](/de/core-concepts/astro-pages/#nicht-html-seiten). Dies ermöglicht statische Feeds _und_ die On-Demand-Generierung bei Verwendung eines [SSR-Adapters](/de/guides/server-side-rendering/).
 
 1. Installiere `@astrojs/rss` mit deinem bevorzugten Paketmanager:
 

src/content/docs/en/core-concepts/endpoints.mdx

@@ -99,7 +99,7 @@ But, unlike in `static` mode, when you configure `server` mode, the endpoints wi
 <RecipeLinks slugs={["en/recipes/call-endpoints" ]}/>
 
 :::note
-Be sure to [enable SSR](/en/guides/server-side-rendering/#enabling-ssr-in-your-project) before trying these examples.
+Be sure to [enable SSR](/en/guides/server-side-rendering/) before trying these examples.
 :::
 
 Server endpoints can access `params` without exporting `getStaticPaths`, and they can return a [`Response`](https://developer.mozilla.org/en-US/docs/Web/API/Response) object, allowing you to set status codes and headers:

src/content/docs/en/guides/backend/google-firebase.mdx

@@ -19,7 +19,7 @@ See our separate guide for [deploying to Firebase hosting](/en/guides/deploy/goo
 ### Prerequisites
 
 - A [Firebase project with a web app configured](https://firebase.google.com/docs/web/setup).
-- An Astro project with [server-side rendering (SSR)](/en/guides/server-side-rendering/#enabling-ssr-in-your-project) enabled.
+- An Astro project with [server-side rendering (SSR)](/en/guides/server-side-rendering/) enabled.
 - Firebase credentials: You will need two sets of credentials to connect Astro to Firebase:
   - Web app credentials: These credentials will be used by the client side of your app. You can find them in the Firebase console under *Project settings > General*. Scroll down to the **Your apps** section and click on the **Web app** icon.
   - Project credentials: These credentials will be used by the server side of your app. You can generate them in the Firebase console under *Project settings > Service accounts > Firebase Admin SDK > Generate new private key*.

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

@@ -428,7 +428,7 @@ Navigate to http://localhost:4321/ and click on one of your posts to make sure y
 
 #### Server side rendering
 
-If you've [opted in to SSR mode](/en/guides/server-side-rendering/#enabling-ssr-in-your-project), you will use a dynamic route that uses a `slug` parameter to fetch the data from Contentful.
+If you've [opted in to SSR mode](/en/guides/server-side-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`: 
 

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

@@ -23,7 +23,7 @@ Select the Astro template, and you'll be ready to [deploy](#deploying-keystatic-
 
 ## Prerequisites
 
-- An existing Astro project [with server-side rendering (SSR) and `output: 'hybrid'` configured](/en/guides/server-side-rendering/#enabling-ssr-in-your-project).
+- An existing Astro project [with server-side rendering (SSR) and `output: 'hybrid'` configured](/en/guides/server-side-rendering/).
 
 :::note
 If you intend to sync Keystatic's data with GitHub, you will also need **a GitHub account with `write` permissions** on the repository for this project.

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

@@ -451,7 +451,7 @@ When adding folders inside of Storyblok, include them in the slug when interacti
 
 #### Server-side rendering
 
-If you’ve [opted into SSR mode](/en/guides/server-side-rendering/#enabling-ssr-in-your-project), you will use dynamic routes to fetch the page data from Storyblok.
+If you’ve [opted into SSR mode](/en/guides/server-side-rendering/), you will use dynamic routes to fetch the page data from Storyblok.
 
 Create a new directory `src/pages/blog/` and add a new file called `[...slug].astro` with the following code:
 

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

@@ -318,7 +318,7 @@ Make sure to choose the right rendering for your content. For markdown check out
 
 #### Server-side rendering
 
-If you've [opted into SSR mode](/en/guides/server-side-rendering/#enabling-ssr-in-your-project) with `output: server` or `output: hybrid`, [generate your dynamic routes](/en/core-concepts/routing/#server-ssr-mode) using the following code:
+If you've [opted into SSR mode](/en/guides/server-side-rendering/) with `output: server` or `output: hybrid`, [generate your dynamic routes](/en/core-concepts/routing/#server-ssr-mode) using the following code:
 
 Create the `src/pages/blog/[slug].astro` file:
 

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

@@ -78,7 +78,7 @@ By default, the build output will be placed at `dist/`. This location can be cha
 :::note
 Before deploying your Astro site with [SSR (server-side rendering)](/en/guides/server-side-rendering/) enabled, make sure you have:
 
-- Installed the [appropriate adapter](/en/guides/server-side-rendering/#enabling-ssr-in-your-project) to your project dependencies (either manually, or using the adapter's `astro add` command, e.g. `npx astro add netlify`).
+- Installed the [appropriate adapter](/en/guides/server-side-rendering/) to your project dependencies (either manually, or using the adapter's `astro add` command, e.g. `npx astro add netlify`).
 - [Added the adapter](/en/reference/configuration-reference/#integrations) to your `astro.config.mjs` file's import and default export when installing manually. (The `astro add` command will take care of this step for you!)
 :::
 

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

@@ -217,7 +217,7 @@ Astro supports loading WASM files directly into your application using the brows
 
 ## Node Builtins
 
-We encourage Astro users to avoid Node.js builtins (`fs`, `path`, etc.) whenever possible. Astro is compatible with multiple runtimes using [adapters](/en/guides/server-side-rendering/#adding-an-adapter). This includes [Deno](https://github.com/denoland/deno-astro-adapter) and [Cloudflare Workers](/en/guides/integrations-guide/cloudflare/) which do not support Node builtin modules such as `fs`.
+We encourage Astro users to avoid Node.js builtins (`fs`, `path`, etc.) whenever possible. Astro is compatible with multiple runtimes using [adapters](/en/guides/server-side-rendering/). This includes [Deno](https://github.com/denoland/deno-astro-adapter) and [Cloudflare Workers](/en/guides/integrations-guide/cloudflare/) which do not support Node builtin modules such as `fs`.
 
 Our aim is to provide Astro alternatives to common Node.js builtins. However, no such alternatives exist today. So, if you _really_ need to use these builtin modules we don't want to stop you. Astro supports Node.js builtins using Node’s newer `node:` prefix. If you want to read a file, for example, you can do so like this:
 

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

@@ -8,4 +8,4 @@ The Deno adapter allows Astro to deploy your SSR site to Deno targets including
 
 The Deno adapter was previously maintained by Astro but now is maintained by Deno directly. Usage is now documented [in the Deno adapter repository](https://github.com/denoland/deno-astro-adapter).
 
-If you are currently using this Astro adapter, you will need to migrate to the new Deno version or to [add another adapter](/en/guides/server-side-rendering/#adding-an-adapter) to continue using SSR in your project.
+If you are currently using this Astro adapter, you will need to migrate to the new Deno version or to [add another adapter](/en/guides/server-side-rendering/) to continue using SSR in your project.

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

@@ -239,7 +239,7 @@ Gatsby has several top-level configuration files that also include site and page
 
 - `gatsby-node.js`: You will not need to create your own nodes in Astro, but viewing the schema in this file may help you with defining types in your Astro project.
 
-- `gatsby-ssr.js`: If you choose to use SSR in Astro, you will [add and configure the SSR adapter](/en/guides/server-side-rendering/#adding-an-adapter) of your choice directly in `astro.config.mjs`.
+- `gatsby-ssr.js`: If you choose to use SSR in Astro, you will [add and configure the SSR adapter](/en/guides/server-side-rendering/) of your choice directly in `astro.config.mjs`.
 
 ## Reference: Convert to Astro Syntax
 

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

@@ -12,7 +12,7 @@ Astro supports fast, automatic RSS feed generation for blogs and other content w
 
 ## Setting up `@astrojs/rss`
 
-The package [`@astrojs/rss`](https://github.com/withastro/astro/tree/main/packages/astro-rss) provides helpers for generating RSS feeds using [API endpoints](/en/core-concepts/endpoints/#static-file-endpoints). This unlocks both static builds _and_ on-demand generation when using an [SSR adapter](/en/guides/server-side-rendering/#adding-an-adapter).
+The package [`@astrojs/rss`](https://github.com/withastro/astro/tree/main/packages/astro-rss) provides helpers for generating RSS feeds using [API endpoints](/en/core-concepts/endpoints/#static-file-endpoints). This unlocks both static builds _and_ on-demand generation when using an [SSR adapter](/en/guides/server-side-rendering/).
 
 1. Install `@astrojs/rss` using your preferred package manager:
 

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

@@ -6,7 +6,7 @@ import Since from '~/components/Since.astro';
 import FileTree from '~/components/FileTree.astro';
 
 
-Astro is designed to make it easy to deploy to any cloud provider for SSR (server-side rendering). This ability is provided by __adapters__, which are [integrations](/en/reference/integrations-reference/). See the [SSR guide](/en/guides/server-side-rendering/#adding-an-adapter) to learn how to use an existing adapter.
+Astro is designed to make it easy to deploy to any cloud provider for SSR (server-side rendering). This ability is provided by __adapters__, which are [integrations](/en/reference/integrations-reference/). See the [SSR guide](/en/guides/server-side-rendering/) to learn how to use an existing adapter.
 
 ## What is an adapter
 

src/content/docs/en/reference/errors/no-adapter-installed.mdx

@@ -20,6 +20,6 @@ To use server-side rendering, an adapter needs to be installed so Astro knows ho
 
 **See Also:**
 -  [Server-side Rendering](/en/guides/server-side-rendering/)
--  [Adding an Adapter](/en/guides/server-side-rendering/#adding-an-adapter)
+-  [Adding an Adapter](/en/guides/server-side-rendering/)
 
 

src/content/docs/en/reference/errors/static-client-address-not-available.mdx

@@ -21,7 +21,7 @@ The `Astro.clientAddress` property is only available when [Server-side rendering
 To get the user's IP address in static mode, different APIs such as [Ipify](https://www.ipify.org/) can be used in a [Client-side script](/en/guides/client-side-scripts/) or it may be possible to get the user's IP using a serverless function hosted on your hosting provider.
 
 **See Also:**
--  [Enabling SSR in Your Project](/en/guides/server-side-rendering/#enabling-ssr-in-your-project)
+-  [Enabling SSR in Your Project](/en/guides/server-side-rendering/)
 -  [Astro.clientAddress](/en/reference/api-reference/#astroclientaddress)
 
 

src/content/docs/en/reference/errors/static-redirect-not-available.mdx

@@ -25,7 +25,7 @@ The `Astro.redirect` function is only available when [Server-side rendering](/en
 To redirect on a static website, the [meta refresh attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta) can be used. Certain hosts also provide config-based redirects (ex: [Netlify redirects](https://docs.netlify.com/routing/redirects/)).
 
 **See Also:**
--  [Enabling SSR in Your Project](/en/guides/server-side-rendering/#enabling-ssr-in-your-project)
+-  [Enabling SSR in Your Project](/en/guides/server-side-rendering/)
 -  [Astro.redirect](/en/reference/api-reference/#astroredirect)
 
 

src/content/docs/es/core-concepts/endpoints.mdx

@@ -98,7 +98,7 @@ Pero, a diferencia del modo `static`, cuando configuras el modo `server`, los en
 <RecipeLinks slugs={["es/recipes/call-endpoints"]}/>
 
 :::note
-Asegúrate de [habilitar SSR](/es/guides/server-side-rendering/#habilitando-ssr-en-tu-proyecto) antes de probar estos ejemplos.
+Asegúrate de [habilitar SSR](/es/guides/server-side-rendering/) antes de probar estos ejemplos.
 :::
 
 Los endpoints del servidor pueden acceder a `params` sin exportar `getStaticPaths`, y pueden retornar un objeto [`Response`](https://developer.mozilla.org/es/docs/Web/API/Response), lo que te permite establecer códigos de estado y encabezados:

src/content/docs/es/guides/backend/google-firebase.mdx

@@ -19,7 +19,7 @@ Consulta nuestra guía independiente para [desplegar en Firebase Hosting](/es/gu
 ### Prerrequesitos
 
 - Un [proyecto de Firebase con una aplicación web configurada](https://firebase.google.com/docs/web/setup).
-- Un proyecto de Astro con [renderizado del lado del servidor (SSR)](/es/guides/server-side-rendering/#habilitando-ssr-en-tu-proyecto) habilitado.
+- Un proyecto de Astro con [renderizado del lado del servidor (SSR)](/es/guides/server-side-rendering/) habilitado.
 - Credenciales de Firebase: Necesitarás dos conjuntos de credenciales para conectar Astro a Firebase:
   - Credenciales de la aplicación web: Estas credenciales serán utilizadas por el lado del cliente de tu aplicación. Puedes encontrarlas en la consola de Firebase en *Project settings > General*. Desplázate hacia abajo hasta la sección **Your apps** y haz clic en el icono de **Web app**.
   - Credenciales del proyecto: Estas credenciales serán utilizadas por el lado del servidor de tu aplicación. Puedes generarlas en la consola de Firebase en *Project settings > Service accounts > Firebase Admin SDK > Generate new private key*.

src/content/docs/es/guides/cms/contentful.mdx

@@ -430,7 +430,7 @@ Navega a http://localhost:4321/ y haz clic en uno de tus artículos para asegura
 
 #### Renderizado del lado del servidor
 
-Si has [optado por el modo SSR](/es/guides/server-side-rendering/#habilitando-ssr-en-tu-proyecto), usarás una ruta dinámica que usa un parámetro `slug` para obtener los datos de Contentful.
+Si has [optado por el modo SSR](/es/guides/server-side-rendering/), usarás una ruta dinámica que usa un parámetro `slug` para obtener los datos de Contentful.
 
 Crea un archivo nuevo llamado `[slug].astro` en `src/pages/posts/`. Usa [`Astro.params`](/es/reference/api-reference/#astroparams) para obtener el slug de la URL, luego pásalo a `getEntries`:
 

src/content/docs/es/guides/cms/storyblok.mdx

@@ -453,7 +453,7 @@ Cuando agregues carpetas dentro de Storyblok, inclúyelas en el slug al interact
 
 #### Renderizado en el lado del servidor
 
-Si has [optado por el modo de SSR](/es/guides/server-side-rendering/#habilitando-ssr-en-tu-proyecto), utilizarás rutas dinámicas para obtener los datos de la página desde Storyblok.
+Si has [optado por el modo de SSR](/es/guides/server-side-rendering/), utilizarás rutas dinámicas para obtener los datos de la página desde Storyblok.
 
 Crea un nuevo directorio `src/pages/blog/` y agrega un nuevo archivo llamado `[...slug].astro` con el siguiente código: