update Sapper links to point to sapper-legacy

Conduitry · Conduitry · commit b21e7b90ad7f · 2019-05-24T09:58:09.000-04:00
diff --git a/content/blog/2017-12-31-sapper-towards-the-ideal-web-app-framework.md b/content/blog/2017-12-31-sapper-towards-the-ideal-web-app-framework.md
@@ -6,7 +6,7 @@ author: Rich Harris
 authorURL: https://twitter.com/Rich_Harris
 ---
 
-> Quickstart for the impatient: [the Sapper docs](https://sapper.svelte.technology), and the [starter template](https://github.com/sveltejs/sapper-template)
+> Quickstart for the impatient: [the Sapper docs](https://sapper-legacy.svelte.dev), and the [starter template](https://github.com/sveltejs/sapper-template)
 
 If you had to list the characteristics of the perfect Node.js web application framework, you'd probably come up with something like this:
 
@@ -48,9 +48,9 @@ What happens if we use the new model as a starting point?
 
 ## Introducing Sapper
 
-<aside>The [name comes from](https://sapper.svelte.technology/guide#why-the-name-) the term for combat engineers, and is also short for <strong>S</strong>velte <strong>app</strong> mak<strong>er</strong></aside>
+<aside>The [name comes from](https://sapper-legacy.svelte.dev/guide#why-the-name-) the term for combat engineers, and is also short for <strong>S</strong>velte <strong>app</strong> mak<strong>er</strong></aside>
 
-[Sapper](https://sapper.svelte.technology) is the answer to that question. **Sapper is a Next.js-style framework that aims to meet the eleven criteria at the top of this article while dramatically reducing the amount of code that gets sent to the browser.** It's implemented as Express-compatible middleware, meaning it's easy to understand and customise.
+[Sapper](https://sapper-legacy.svelte.dev) is the answer to that question. **Sapper is a Next.js-style framework that aims to meet the eleven criteria at the top of this article while dramatically reducing the amount of code that gets sent to the browser.** It's implemented as Express-compatible middleware, meaning it's easy to understand and customise.
 
 The same 'hello world' app that took 204kb with React and Next weighs just 7kb with Sapper. That number is likely to fall further in the future as we explore the space of optimisation possibilities, such as not shipping any JavaScript *at all* for pages that aren't interactive, beyond the tiny Sapper runtime that handles client-side routing.
 
diff --git a/content/blog/2018-04-18-version-2.md b/content/blog/2018-04-18-version-2.md
@@ -56,7 +56,7 @@ There are a few other updates. But you don't need to make them manually — just
 npx svelte-upgrade v2 src
 ```
 
-This assumes any `.html` files in `src` are Svelte components. You can specify whichever directory you like, or target a different directory — for example, you'd do `npx svelte-upgrade v2 routes` to update a [Sapper](https://sapper.svelte.technology) app.
+This assumes any `.html` files in `src` are Svelte components. You can specify whichever directory you like, or target a different directory — for example, you'd do `npx svelte-upgrade v2 routes` to update a [Sapper](https://sapper-legacy.svelte.dev) app.
 
 To see the full set of changes, consult the [svelte-upgrade README](https://github.com/sveltejs/svelte-upgrade#svelte-v2-syntax-changes).
 
diff --git a/content/guide/06-special-components.md b/content/guide/06-special-components.md
@@ -174,7 +174,7 @@ The `<svelte:document>` tag, just like `<svelte:window>`, gives you a convenient
 
 ### `<svelte:head>`
 
-If you're building an application with Svelte — particularly if you're using [Sapper](https://sapper.svelte.technology) — then it's likely you'll need to add some content to the `<head>` of your page, such as adding a `<title>` element.
+If you're building an application with Svelte — particularly if you're using [Sapper](https://sapper-legacy.svelte.dev) — then it's likely you'll need to add some content to the `<head>` of your page, such as adding a `<title>` element.
 
 You can do that with the `<svelte:head>` tag:
 
diff --git a/content/guide/09-static-properties.md b/content/guide/09-static-properties.md
@@ -32,6 +32,6 @@ In some situations, you might want to add static properties to your component co
 
 ### preload
 
-If your component definition includes a `preload` function, it will be attached to the component constructor as a static method. It doesn't change the behaviour of your component in any way — instead, it's a convention that allows systems like [Sapper](https://sapper.svelte.technology) to delay rendering of a component until its data is ready.
+If your component definition includes a `preload` function, it will be attached to the component constructor as a static method. It doesn't change the behaviour of your component in any way — instead, it's a convention that allows systems like [Sapper](https://sapper-legacy.svelte.dev) to delay rendering of a component until its data is ready.
 
-See the section on [preloading](https://sapper.svelte.technology/guide#preloading) in the Sapper docs for more information.
+See the section on [preloading](https://sapper-legacy.svelte.dev/guide#preloading) in the Sapper docs for more information.
diff --git a/src/components/Nav.html b/src/components/Nav.html
@@ -10,7 +10,7 @@
 		<li><a rel='prefetch' class='{segment === "guide" ? "active": ""}' href='guide'>Guide</a></li>
 		<li><a rel='prefetch' class='{segment === "repl" ? "active": ""}' href='repl'>REPL</a></li>
 		<li><a rel='prefetch' class='{segment === "blog" ? "active": ""}' href='blog'>Blog</a></li>
-		<li><a href='https://sapper.svelte.technology'>Sapper</a></li>
+		<li><a href='https://sapper-legacy.svelte.dev'>Sapper</a></li>
 		<li><a href='https://discord.gg/yy75DKs'>Chat</a></li>
 		<li><a href='https://github.com/sveltejs/svelte'>GitHub</a></li>
 	</ul>
