From 0b38c0278cc5ff94e0f6e233e1daf2a307599a2c Mon Sep 17 00:00:00 2001 From: Ben McCann <322311+benmccann@users.noreply.github.com> Date: Wed, 23 Oct 2024 16:48:06 -0700 Subject: [PATCH 1/8] chore: update links to learn.svelte.dev --- .../blog/2022-07-01-whats-new-in-svelte-july-2022.md | 2 +- .../content/blog/2022-12-14-announcing-sveltekit-1.0.md | 4 ++-- .../blog/2023-01-01-whats-new-in-svelte-january-2023.md | 4 ++-- apps/svelte.dev/content/blog/2023-06-22-svelte-4.md | 6 +++--- .../content/blog/2023-06-29-svelte-dev-overhaul.md | 6 +++--- apps/svelte.dev/content/blog/2023-09-20-runes.md | 4 ++-- 6 files changed, 13 insertions(+), 13 deletions(-) diff --git a/apps/svelte.dev/content/blog/2022-07-01-whats-new-in-svelte-july-2022.md b/apps/svelte.dev/content/blog/2022-07-01-whats-new-in-svelte-july-2022.md index 44e30689ad..b50e791c68 100644 --- a/apps/svelte.dev/content/blog/2022-07-01-whats-new-in-svelte-july-2022.md +++ b/apps/svelte.dev/content/blog/2022-07-01-whats-new-in-svelte-july-2022.md @@ -17,7 +17,7 @@ We will also be utilizing OpenCollective funds to allow Svelte core maintainers ## What's new in Svelte & Language Tools -- [learn.svelte.dev](https://learn.svelte.dev/) is a new way to learn Svelte and SvelteKit from the ground up that is currently in development +- [The tutorial](/tutorial) is a new way to learn Svelte and SvelteKit from the ground up that is currently in development - Faster SSR is coming in the next Svelte release. A PR two years in the making, resulting in up to 3x faster rendering in some benchmarking tests! ([PR](https://github.com/sveltejs/svelte/pull/5701)) - "Find File References" ([0.14.28](https://github.com/sveltejs/language-tools/releases/tag/language-server-0.14.28)) and "Find Component References" ([0.14.29](https://github.com/sveltejs/language-tools/releases/tag/language-server-0.14.29)) in the latest versions of the Svelte extension shows where Svelte files and components have been imported and used ([Demo](https://twitter.com/dummdidumm_/status/1532459709604716544/photo/1)) - The Svelte extension now supports CSS path completion ([0.14.29](https://github.com/sveltejs/language-tools/releases/tag/language-server-0.14.29)) diff --git a/apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md b/apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md index 0b8f081ef7..ad5045e272 100644 --- a/apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md +++ b/apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md @@ -9,7 +9,7 @@ After two years in development, [SvelteKit](https://kit.svelte.dev) has finally We’re so excited to share this release with you. It’s the culmination of thousands of hours of work, both from the Svelte core team and the wider community, and we think it’s the most enjoyable way to build production-grade websites, whether you’re a solo developer working on a small project or part of a large team. -To get started, run `npm create svelte@latest`, and visit the [docs](https://kit.svelte.dev/docs) and (experimental!) [interactive tutorial](https://learn.svelte.dev). +To get started, run `npm create svelte@latest`, and visit the [docs](https://kit.svelte.dev/docs) and (experimental!) [interactive tutorial](/tutorial).
@@ -88,7 +88,7 @@ Back in early 2021, when we adopted Vite, we were the first major application fr We’ve had terrific support from teams at [Vercel](https://vercel.com), [Netlify](https://netlify.app/) and [Cloudflare](https://www.cloudflare.com/) to make zero-config deployments for those platforms possible. -Our friends at [StackBlitz](https://stackblitz.com/) worked feverishly to make [learn.svelte.dev](https://learn.svelte.dev), our first-of-its-kind [WebContainer](https://blog.stackblitz.com/posts/introducing-webcontainers/)-powered interactive tutorial, a reality. +Our friends at [StackBlitz](https://stackblitz.com/) worked feverishly to make [our new tutorial](/tutorial), the first-of-its-kind [WebContainer](https://blog.stackblitz.com/posts/introducing-webcontainers/)-powered interactive tutorial, a reality. Finally, none of this could have happened without the project’s financial supporters. This includes hundreds of backers on [Open Collective](https://opencollective.com/svelte), and Vercel, which employs two core developers ([Rich](https://twitter.com/Rich_Harris/) and [Simon](https://twitter.com/dummdidumm_/)) to work on Svelte full time and supports the project in many other ways, such as [Steph’s](https://twitter.com/steph_dietz_) [Beginner SvelteKit](https://vercel.com/docs/beginner-sveltekit) course. diff --git a/apps/svelte.dev/content/blog/2023-01-01-whats-new-in-svelte-january-2023.md b/apps/svelte.dev/content/blog/2023-01-01-whats-new-in-svelte-january-2023.md index 401bf0516b..9f3ee60609 100644 --- a/apps/svelte.dev/content/blog/2023-01-01-whats-new-in-svelte-january-2023.md +++ b/apps/svelte.dev/content/blog/2023-01-01-whats-new-in-svelte-january-2023.md @@ -1,11 +1,11 @@ --- title: "What's new in Svelte: January 2023" -description: 'SvelteKit 1.0, learn.svelte.dev, and type definitions for Svelte elements.' +description: 'SvelteKit 1.0, tutorial, and type definitions for Svelte elements.' author: Dani Sandoval authorURL: https://dreamindani.com --- -It's been just two weeks since the release of [SvelteKit 1.0](https://svelte.dev/blog/announcing-sveltekit-1.0)! If you haven't yet, check out the [livestream](https://www.youtube.com/watch?v=N4BRVkQVoMc), [new website](https://kit.svelte.dev/) and [learn.svelte.dev](https://learn.svelte.dev/) to learn all the features of SvelteKit step-by-step. +It's been just two weeks since the release of [SvelteKit 1.0](https://svelte.dev/blog/announcing-sveltekit-1.0)! If you haven't yet, check out the [livestream](https://www.youtube.com/watch?v=N4BRVkQVoMc), [new website](https://kit.svelte.dev/) and [tutorial](/tutorial) to learn all the features of SvelteKit step-by-step. Let's dive into the details... diff --git a/apps/svelte.dev/content/blog/2023-06-22-svelte-4.md b/apps/svelte.dev/content/blog/2023-06-22-svelte-4.md index 7eb2bd8342..b74f6173ea 100644 --- a/apps/svelte.dev/content/blog/2023-06-22-svelte-4.md +++ b/apps/svelte.dev/content/blog/2023-06-22-svelte-4.md @@ -9,7 +9,7 @@ After months in the making, we're excited to announce the stable release of Svel Time flies - Svelte 3 was released more than four years ago! In JavaScript-framework-time, that's eons. Svelte’s freshness has persisted throughout, but Node.js and browser APIs have evolved during that time and today we’re updating Svelte to take advantage of some of these improvements. Svelte 4 is mainly a maintenance release, bumping minimum version requirements and tightening up the design in specific areas. It sets the stage for the next generation of Svelte to be released as Svelte 5 - we think you’ll love it. -If you haven't tried Svelte yet, take it for a spin in our [interactive tutorial](https://learn.svelte.dev/), on [StackBlitz](https://sveltekit.new/), or locally with `npm create svelte@latest`. Svelte lets you easily put together web UIs leveraging the power of HTML, CSS, JS, and the Svelte compiler. Watch [Svelte Radio Live](https://www.youtube.com/watch?v=72TIVhRtyWE) to learn more about this release. +If you haven't tried Svelte yet, take it for a spin in our [interactive tutorial](/tutorial), on [StackBlitz](https://sveltekit.new/), or locally with `npm create svelte@latest`. Svelte lets you easily put together web UIs leveraging the power of HTML, CSS, JS, and the Svelte compiler. Watch [Svelte Radio Live](https://www.youtube.com/watch?v=72TIVhRtyWE) to learn more about this release. ## What's new @@ -17,7 +17,7 @@ If you haven't tried Svelte yet, take it for a spin in our [interactive tutorial This release results in smaller and faster hydration code. To see the impact, SvelteKit users can see their compiled output shrink in size by examining the `.svelte-kit/output/client/_app/immutable/nodes` folder. For example, on [kit.svelte.dev](https://kit.svelte.dev) the JS generated across the whole site was reduced in size by 12.7% (126.3 kB to 110.2 kB). -Svelte 4 reduces the Svelte package size by nearly 75% (10.6 MB down to 2.8 MB), which means less waiting on `npm install`. This improvement will be especially noticeable for users who are loading our interactive learning experience on [learn.svelte.dev](https://learn.svelte.dev) for the first time, users of the Svelte REPL, and users with limited connectivity. The majority of the remaining package size is eslint support, which necessitates distributing a CJS build, and once [the eslint rewrite](https://github.com/eslint/eslint/discussions/16557) is completed the Svelte package size can drop by over another 50%. +Svelte 4 reduces the Svelte package size by nearly 75% (10.6 MB down to 2.8 MB), which means less waiting on `npm install`. This improvement will be especially noticeable for users who are loading [our interactive learning experience](/tutorial) for the first time, users of the Svelte REPL, and users with limited connectivity. The majority of the remaining package size is eslint support, which necessitates distributing a CJS build, and once [the eslint rewrite](https://github.com/eslint/eslint/discussions/16557) is completed the Svelte package size can drop by over another 50%. The number of dependencies in Svelte has been greatly reduced from 61 down to 16. This means faster downloads for our users as well as less susceptibility to supply chain attacks. We also slightly reduced the number of dependencies in the latest versions of SvelteKit as well. @@ -34,7 +34,7 @@ auto-imports now work more reliably ### Updated site, docs, and tutorial -The official [svelte.dev](https://svelte.dev) site has gotten an overhaul. It’s now split into multiple pages with improved mobile nav, overhauled typescript docs, dark mode, and an enhanced REPL. The SvelteKit site is also being updated to match. And we’ve updated all the tutorial links to point to our new [learn.svelte.dev](https://learn.svelte.dev) experience. The old tutorial remains available for users of Safari 16.3 and earlier. +The official [svelte.dev](https://svelte.dev) site has gotten an overhaul. It’s now split into multiple pages with improved mobile nav, overhauled typescript docs, dark mode, and an enhanced REPL. The SvelteKit site is also being updated to match. And we’ve updated all the tutorial links to point to our new [tutorial](/tutorial) experience. The old tutorial remains available for users of Safari 16.3 and earlier. Stay tuned for a more in-depth blog post about all the site changes in the coming days! diff --git a/apps/svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md b/apps/svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md index a3ffd739bf..4e2892d0d0 100644 --- a/apps/svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md +++ b/apps/svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md @@ -81,9 +81,9 @@ If you're on mobile, you can already see it at the bottom. If you're on desktop, ## Unification of Svelte websites -Now [svelte.dev](https://svelte.dev), [kit.svelte.dev](https://kit.svelte.dev), and [learn.svelte.dev](https://learn.svelte.dev) all use the same design system and are more consistent with each other. This makes it easier to navigate between the websites and also makes it easier to maintain them. We have a package shared across the sites called `@sveltejs/site-kit`, which went through rigorous changes over last 4 months as we have been moving all common code into this package. +Now [svelte.dev](https://svelte.dev), [kit.svelte.dev](https://kit.svelte.dev), and [the tutorial](/tutorial) all use the same design system and are more consistent with each other. This makes it easier to navigate between the websites and also makes it easier to maintain them. We have a package shared across the sites called `@sveltejs/site-kit`, which went through rigorous changes over last 4 months as we have been moving all common code into this package. -For example, we implemented the dark mode toggle in `@sveltejs/site-kit`. We then simply updated the package on [learn.svelte.dev](https://learn.svelte.dev) and [kit.svelte.dev](https://kit.svelte.dev) and those sites got the dark mode toggle automatically (this is also the reason why those sites got the dark mode toggle before the [svelte.dev](https://svelte.dev) relaunch). +For example, we implemented the dark mode toggle in `@sveltejs/site-kit`. We then simply updated the package for [the tutorial](/tutorial) and [kit.svelte.dev](https://kit.svelte.dev) and those sites got the dark mode toggle automatically (this is also the reason why those sites got the dark mode toggle before the [svelte.dev](https://svelte.dev) relaunch). ## What's next @@ -92,5 +92,5 @@ We have many more things planned to do post-launch. Some of them are: - Redesigned blog page - Improved search - Playground: a unified REPL and Examples page -- Unify the infrastructure of the Svelte REPL and [learn.svelte.dev](https://learn.svelte.dev) by creating a webcontainer-based REPL with rollup as a fallback +- Unify the infrastructure of the Svelte REPL and [the tutorial](/tutorial) by creating a webcontainer-based REPL with rollup as a fallback - Address any feedback diff --git a/apps/svelte.dev/content/blog/2023-09-20-runes.md b/apps/svelte.dev/content/blog/2023-09-20-runes.md index b4e719895d..01c8ed35e3 100644 --- a/apps/svelte.dev/content/blog/2023-09-20-runes.md +++ b/apps/svelte.dev/content/blog/2023-09-20-runes.md @@ -72,11 +72,11 @@ For example, to declare a piece of reactive state, we can use the `$state` rune: At first glance, this might seem like a step back — perhaps even [un-Svelte-like](https://twitter.com/stolinski/status/1438173489479958536). Isn't it better if `let count` is reactive by default? -Well, no. The reality is that as applications grow in complexity, figuring out which values are reactive and which aren't can get tricky. And the heuristic only works for `let` declarations at the top level of a component, which can cause confusion. Having code behave one way inside `.svelte` files and another inside `.js` can make it hard to refactor code, for example if you need to turn something into a [store](https://learn.svelte.dev/tutorial/writable-stores) so that you can use it in multiple places. +Well, no. The reality is that as applications grow in complexity, figuring out which values are reactive and which aren't can get tricky. And the heuristic only works for `let` declarations at the top level of a component, which can cause confusion. Having code behave one way inside `.svelte` files and another inside `.js` can make it hard to refactor code, for example if you need to turn something into a [store](/tutorial/svelte/writable-stores) so that you can use it in multiple places. ## Beyond components -With runes, reactivity extends beyond the boundaries of your `.svelte` files. Suppose we wanted to encapsulate our counter logic in a way that could be reused between components. Today, you would use a [custom store](https://learn.svelte.dev/tutorial/custom-stores) in a `.js` or `.ts` file: +With runes, reactivity extends beyond the boundaries of your `.svelte` files. Suppose we wanted to encapsulate our counter logic in a way that could be reused between components. Today, you would use a [custom store](/tutorial/svelte/custom-stores) in a `.js` or `.ts` file: ```js /// file: counter.js From 73c7d14abdbbe0a5d100f9dad28160b28c38d7d1 Mon Sep 17 00:00:00 2001 From: Ben McCann <322311+benmccann@users.noreply.github.com> Date: Wed, 23 Oct 2024 16:56:29 -0700 Subject: [PATCH 2/8] fix --- apps/svelte.dev/content/blog/2023-09-20-runes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/svelte.dev/content/blog/2023-09-20-runes.md b/apps/svelte.dev/content/blog/2023-09-20-runes.md index 01c8ed35e3..2673d47259 100644 --- a/apps/svelte.dev/content/blog/2023-09-20-runes.md +++ b/apps/svelte.dev/content/blog/2023-09-20-runes.md @@ -72,7 +72,7 @@ For example, to declare a piece of reactive state, we can use the `$state` rune: At first glance, this might seem like a step back — perhaps even [un-Svelte-like](https://twitter.com/stolinski/status/1438173489479958536). Isn't it better if `let count` is reactive by default? -Well, no. The reality is that as applications grow in complexity, figuring out which values are reactive and which aren't can get tricky. And the heuristic only works for `let` declarations at the top level of a component, which can cause confusion. Having code behave one way inside `.svelte` files and another inside `.js` can make it hard to refactor code, for example if you need to turn something into a [store](/tutorial/svelte/writable-stores) so that you can use it in multiple places. +Well, no. The reality is that as applications grow in complexity, figuring out which values are reactive and which aren't can get tricky. And the heuristic only works for `let` declarations at the top level of a component, which can cause confusion. Having code behave one way inside `.svelte` files and another inside `.js` can make it hard to refactor code, for example if you need to turn something into a [store](/tutorial/svelte/introducing-stores) so that you can use it in multiple places. ## Beyond components From b0828f3482b015e38c48074ff380a8a552cfa942 Mon Sep 17 00:00:00 2001 From: Ben McCann <322311+benmccann@users.noreply.github.com> Date: Wed, 23 Oct 2024 17:01:18 -0700 Subject: [PATCH 3/8] remove mention of old tutorial --- apps/svelte.dev/content/blog/2023-06-22-svelte-4.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/svelte.dev/content/blog/2023-06-22-svelte-4.md b/apps/svelte.dev/content/blog/2023-06-22-svelte-4.md index b74f6173ea..3b87513644 100644 --- a/apps/svelte.dev/content/blog/2023-06-22-svelte-4.md +++ b/apps/svelte.dev/content/blog/2023-06-22-svelte-4.md @@ -34,7 +34,7 @@ auto-imports now work more reliably ### Updated site, docs, and tutorial -The official [svelte.dev](https://svelte.dev) site has gotten an overhaul. It’s now split into multiple pages with improved mobile nav, overhauled typescript docs, dark mode, and an enhanced REPL. The SvelteKit site is also being updated to match. And we’ve updated all the tutorial links to point to our new [tutorial](/tutorial) experience. The old tutorial remains available for users of Safari 16.3 and earlier. +The official [svelte.dev](https://svelte.dev) site has gotten an overhaul. It’s now split into multiple pages with improved mobile nav, overhauled typescript docs, dark mode, and an enhanced REPL. The SvelteKit site is also being updated to match. And we’ve updated all the tutorial links to point to our new [tutorial](/tutorial) experience. Stay tuned for a more in-depth blog post about all the site changes in the coming days! From 66185127d8e9defa8ad5d435fc0e28449341e840 Mon Sep 17 00:00:00 2001 From: Ben McCann <322311+benmccann@users.noreply.github.com> Date: Wed, 23 Oct 2024 17:07:02 -0700 Subject: [PATCH 4/8] fix --- apps/svelte.dev/content/blog/2023-09-20-runes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/svelte.dev/content/blog/2023-09-20-runes.md b/apps/svelte.dev/content/blog/2023-09-20-runes.md index 2673d47259..8c4ae8b7ed 100644 --- a/apps/svelte.dev/content/blog/2023-09-20-runes.md +++ b/apps/svelte.dev/content/blog/2023-09-20-runes.md @@ -76,7 +76,7 @@ Well, no. The reality is that as applications grow in complexity, figuring out w ## Beyond components -With runes, reactivity extends beyond the boundaries of your `.svelte` files. Suppose we wanted to encapsulate our counter logic in a way that could be reused between components. Today, you would use a [custom store](/tutorial/svelte/custom-stores) in a `.js` or `.ts` file: +With runes, reactivity extends beyond the boundaries of your `.svelte` files. Suppose we wanted to encapsulate our counter logic in a way that could be reused between components. Today, you would use a [custom store](/docs/svelte/stores) in a `.js` or `.ts` file: ```js /// file: counter.js From a2d6ecd6b2c13e5aff45b0491a6aab9faec9bfba Mon Sep 17 00:00:00 2001 From: Ben McCann <322311+benmccann@users.noreply.github.com> Date: Thu, 24 Oct 2024 08:54:25 -0700 Subject: [PATCH 5/8] keep a couple of links as they were to avoid changing meaning --- .../svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/apps/svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md b/apps/svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md index 4e2892d0d0..6c343b5d49 100644 --- a/apps/svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md +++ b/apps/svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md @@ -81,9 +81,9 @@ If you're on mobile, you can already see it at the bottom. If you're on desktop, ## Unification of Svelte websites -Now [svelte.dev](https://svelte.dev), [kit.svelte.dev](https://kit.svelte.dev), and [the tutorial](/tutorial) all use the same design system and are more consistent with each other. This makes it easier to navigate between the websites and also makes it easier to maintain them. We have a package shared across the sites called `@sveltejs/site-kit`, which went through rigorous changes over last 4 months as we have been moving all common code into this package. +Now [svelte.dev](https://svelte.dev), [kit.svelte.dev](https://kit.svelte.dev), and [learn.svelte.dev](https://learn.svelte.dev) all use the same design system and are more consistent with each other. This makes it easier to navigate between the websites and also makes it easier to maintain them. We have a package shared across the sites called `@sveltejs/site-kit`, which went through rigorous changes over last 4 months as we have been moving all common code into this package. -For example, we implemented the dark mode toggle in `@sveltejs/site-kit`. We then simply updated the package for [the tutorial](/tutorial) and [kit.svelte.dev](https://kit.svelte.dev) and those sites got the dark mode toggle automatically (this is also the reason why those sites got the dark mode toggle before the [svelte.dev](https://svelte.dev) relaunch). +For example, we implemented the dark mode toggle in `@sveltejs/site-kit`. We then simply updated the package for [learn.svelte.dev](https://learn.svelte.dev) and [kit.svelte.dev](https://kit.svelte.dev) and those sites got the dark mode toggle automatically (this is also the reason why those sites got the dark mode toggle before the [svelte.dev](https://svelte.dev) relaunch). ## What's next From 53bdbd6266b7ea71e62c105af7a3261fe8d9634a Mon Sep 17 00:00:00 2001 From: Ben McCann <322311+benmccann@users.noreply.github.com> Date: Thu, 24 Oct 2024 08:55:50 -0700 Subject: [PATCH 6/8] tweak --- apps/svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md b/apps/svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md index 6c343b5d49..2b9e1ded69 100644 --- a/apps/svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md +++ b/apps/svelte.dev/content/blog/2023-06-29-svelte-dev-overhaul.md @@ -83,7 +83,7 @@ If you're on mobile, you can already see it at the bottom. If you're on desktop, Now [svelte.dev](https://svelte.dev), [kit.svelte.dev](https://kit.svelte.dev), and [learn.svelte.dev](https://learn.svelte.dev) all use the same design system and are more consistent with each other. This makes it easier to navigate between the websites and also makes it easier to maintain them. We have a package shared across the sites called `@sveltejs/site-kit`, which went through rigorous changes over last 4 months as we have been moving all common code into this package. -For example, we implemented the dark mode toggle in `@sveltejs/site-kit`. We then simply updated the package for [learn.svelte.dev](https://learn.svelte.dev) and [kit.svelte.dev](https://kit.svelte.dev) and those sites got the dark mode toggle automatically (this is also the reason why those sites got the dark mode toggle before the [svelte.dev](https://svelte.dev) relaunch). +For example, we implemented the dark mode toggle in `@sveltejs/site-kit`. We then simply updated the package on [learn.svelte.dev](https://learn.svelte.dev) and [kit.svelte.dev](https://kit.svelte.dev) and those sites got the dark mode toggle automatically (this is also the reason why those sites got the dark mode toggle before the [svelte.dev](https://svelte.dev) relaunch). ## What's next From 08fc0ecbcadf32974643b1fc362ef8f47cb1144e Mon Sep 17 00:00:00 2001 From: Ben McCann <322311+benmccann@users.noreply.github.com> Date: Thu, 24 Oct 2024 19:39:41 -0700 Subject: [PATCH 7/8] Update apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md Co-authored-by: Rich Harris --- .../content/blog/2022-12-14-announcing-sveltekit-1.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md b/apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md index e6c6acc899..c3d0e43857 100644 --- a/apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md +++ b/apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md @@ -88,7 +88,7 @@ Back in early 2021, when we adopted Vite, we were the first major application fr We’ve had terrific support from teams at [Vercel](https://vercel.com), [Netlify](https://netlify.app/) and [Cloudflare](https://www.cloudflare.com/) to make zero-config deployments for those platforms possible. -Our friends at [StackBlitz](https://stackblitz.com/) worked feverishly to make [our new tutorial](/tutorial), the first-of-its-kind [WebContainer](https://blog.stackblitz.com/posts/introducing-webcontainers/)-powered interactive tutorial, a reality. +Our friends at [StackBlitz](https://stackblitz.com/) worked feverishly to make [learn.svelte.dev](https://learn.svelte.dev), our first-of-its-kind [WebContainer](https://blog.stackblitz.com/posts/introducing-webcontainers/)-powered interactive tutorial, a reality. Finally, none of this could have happened without the project’s financial supporters. This includes hundreds of backers on [Open Collective](https://opencollective.com/svelte), and Vercel, which employs two core developers ([Rich](https://twitter.com/Rich_Harris/) and [Simon](https://twitter.com/dummdidumm_/)) to work on Svelte full time and supports the project in many other ways, such as [Steph’s](https://twitter.com/steph_dietz_) [Beginner SvelteKit](https://vercel.com/docs/beginner-sveltekit) course. From 68b944d4b573faf0310828dcb433c429a51f5266 Mon Sep 17 00:00:00 2001 From: Ben McCann <322311+benmccann@users.noreply.github.com> Date: Thu, 24 Oct 2024 19:40:20 -0700 Subject: [PATCH 8/8] Update apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md --- .../content/blog/2022-12-14-announcing-sveltekit-1.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md b/apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md index c3d0e43857..3fd84120a8 100644 --- a/apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md +++ b/apps/svelte.dev/content/blog/2022-12-14-announcing-sveltekit-1.0.md @@ -9,7 +9,7 @@ After two years in development, [SvelteKit](https://kit.svelte.dev) has finally We’re so excited to share this release with you. It’s the culmination of thousands of hours of work, both from the Svelte core team and the wider community, and we think it’s the most enjoyable way to build production-grade websites, whether you’re a solo developer working on a small project or part of a large team. -To get started, run `npm create svelte@latest`, and visit the [docs](/docs/kit) and (experimental!) [interactive tutorial](/tutorial). +To get started, run `npm create svelte@latest`, and visit the [docs](/docs/kit) and (experimental!) [interactive tutorial](https://learn.svelte.dev).