docs: clarify that SSR is required for SSG with content (#14471) #14560
+10
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See issue #14471. My main edit here is in the adapter-static (SSG) docs, where I believe a warning should be placed to not disable SSR when trying to achieve SSG.
I also added a few warnings and links in the glossary and page options docs to guide people to the right information when they are researching SSG in SvelteKit.
These changes don't solve the situation that it's conceptually counter-intuitive (to me) that SSG/prerendering requires "SSR", but it tries to help developers to not making unintended mistakes based on wrong assumptions.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpm changeset
and following the prompts. Changesets that add features should beminor
and those that fix bugs should bepatch
. Please prefix changeset messages withfeat:
,fix:
, orchore:
.Edits