From 94ead1b2bc0f43422c2252c644fc8f2785bd0f6b Mon Sep 17 00:00:00 2001 From: Rich Harris Date: Tue, 3 Nov 2020 23:21:16 -0500 Subject: [PATCH] make language less scary --- site/content/blog/2020-11-02-whats-the-deal-with-sveltekit.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/blog/2020-11-02-whats-the-deal-with-sveltekit.md b/site/content/blog/2020-11-02-whats-the-deal-with-sveltekit.md index c800f6b200..238eb657d5 100644 --- a/site/content/blog/2020-11-02-whats-the-deal-with-sveltekit.md +++ b/site/content/blog/2020-11-02-whats-the-deal-with-sveltekit.md @@ -21,7 +21,7 @@ This was slightly tongue-in-cheek — as the talk explains, it's really more of While the Svelte homepage and documentation encourages you to [degit](https://github.com/Rich-Harris/degit) the [sveltejs/template](https://github.com/sveltejs/template) repo to start building an app, Sapper has long been our recommended way to build apps; this very blog post is (at the time of writing!) rendered with Sapper. -## Why is it being wound down? +## Why are we migrating to something new? Firstly, the distinction between [sveltejs/template](https://github.com/sveltejs/template) and [sveltejs/sapper-template](https://github.com/sveltejs/sapper-template) is confusing, particularly to newcomers to Svelte. Having a single recommended way to start building apps with Svelte will bring enormous benefits: we simplify onboarding, reduce the maintenance and support burden, and can potentially begin to explore the new possibilities that are unlocked by having a predictable project structure. (This last part is deliberately vague because it will take time to fully understand what those possibilities are.)