docs: move 'What can I make with SvelteKit' back to FAQ #10547
Merged
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.
This PR places 'What can I make with SvelteKit' content back to the FAQ, originally added in #10380.
I didn't realize this earlier, but it turns out "What can I make with SvelteKit" was moved to its own page during the new site migration: https://kit.svelte.dev/docs/what-can-i-make-with-sveltekit.
If you'd like to keep it that way, then you can disregard this PR.
I have some other drive-by fixes:
/docs/integrations
page now do/faq
now correctly go to/docs/faq
Another issue I found, but unsure how to fix:
./faq#how-do-i-use-a-client-side-only-library-that-depends-on-document-or-window
, but that heading's slug gets generated ashow-do-i-use-x-with-sveltekit-how-do-i-use-a-client-side-only-library-that-depends-on-document-or-window
— since it's a level-3 heading, it somehow merges with its respective level-2 heading's slug. I'm not sure if the generated slug is intentionally merged with its upper header, but I adjusted the link to satisfy the build for now.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:
.