From 795d598aebffe594946c43530188188e1564626d Mon Sep 17 00:00:00 2001 From: Matthew Phillips Date: Fri, 14 Jul 2023 11:47:24 -0400 Subject: [PATCH] Revert "Clarify SSR limitations of sitemaps of dynamic routes (#7625)" (#7653) This reverts commit 9352ac65f4d8c44a5d0cf9cccc37a1196da538cf. --- packages/integrations/sitemap/README.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/packages/integrations/sitemap/README.md b/packages/integrations/sitemap/README.md index 69ae3ea4b8eb..3e46bb7bb324 100644 --- a/packages/integrations/sitemap/README.md +++ b/packages/integrations/sitemap/README.md @@ -19,8 +19,6 @@ A sitemap file is recommended for large multi-page sites. If you don't use a sit With Astro Sitemap, you don't have to worry about creating this file: build your Astro site how you normally would, and the Astro Sitemap integration will crawl your routes and create the sitemap file. -> **Note** > [Dynamic routes](https://docs.astro.build/en/core-concepts/routing/#dynamic-routes) like `[...slug]` or `src/pages/[lang]/[version]/info.astro` will generate sitemap entries for the pages those routes render, _provided that they are rendered statically_ (i.e., using `getStaticPaths()`. But because of the nature of [Astro's SSR mode](https://docs.astro.build/en/guides/server-side-rendering/), any dynamic routes that are server-rendered (via Astro's server or hybrid modes) do not output a static array of pages, so they will _not_ generate corresponding sitemap entries. - ## Installation ### Quick Install