diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
index 5e43e5ca1d..e7bd60d3f4 100644
--- a/.github/ISSUE_TEMPLATE.md
+++ b/.github/ISSUE_TEMPLATE.md
@@ -3,7 +3,7 @@ Thanks for raising an issue! (For *questions*, we recommend instead using https:
 
 To help us help you, if you've found a bug please consider the following:
 
-* If you can demonstrate the bug using https://svelte.technology/repl, please do.
+* If you can demonstrate the bug using https://svelte.dev/repl, please do.
 * If that's not possible, we recommend creating a small repo that illustrates the problem.
 * Make sure you include information about the browser, and which version of Svelte you're using
 
diff --git a/CHANGELOG.md b/CHANGELOG.md
index f9b7a971bb..6b049da08e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -316,7 +316,7 @@
 
 ## 2.0.0
 
-*See [the blog post](https://svelte.technology/blog/version-2) for information on how to upgrade your apps*
+*See [the blog post](https://svelte.dev/blog/version-2) for information on how to upgrade your apps*
 
 * New template syntax ([#1318](https://github.com/sveltejs/svelte/issues/1318))
 * Emit ES2015 code, not ES5 ([#1348](https://github.com/sveltejs/svelte/pull/1348))
diff --git a/site/content/blog/2017-08-07-the-easiest-way-to-get-started.md b/site/content/blog/2017-08-07-the-easiest-way-to-get-started.md
index b29c3cb5c2..915269b817 100644
--- a/site/content/blog/2017-08-07-the-easiest-way-to-get-started.md
+++ b/site/content/blog/2017-08-07-the-easiest-way-to-get-started.md
@@ -12,7 +12,7 @@ Because of that, getting started with it can be a little bit confusing at first.
 
 ## 1. Use the REPL
 
-The [Svelte REPL](https://svelte.technology/repl) is the easiest way to begin. You can choose from a list of examples to get you started, and tweak them until they do what you want.
+The [Svelte REPL](repl) is the easiest way to begin. You can choose from a list of examples to get you started, and tweak them until they do what you want.
 
 <aside><p>You'll need to have <a href="https://nodejs.org/">Node.js</a> installed, and know how to use the terminal</p></aside>
 
diff --git a/site/content/blog/2017-09-06-the-zen-of-just-writing-css.md b/site/content/blog/2017-09-06-the-zen-of-just-writing-css.md
index 4ea56bc633..a467ac3d7f 100644
--- a/site/content/blog/2017-09-06-the-zen-of-just-writing-css.md
+++ b/site/content/blog/2017-09-06-the-zen-of-just-writing-css.md
@@ -28,7 +28,7 @@ The consequence of all this is the **append-only stylesheet**. There's no way of
 The idea behind SFCs is simple: you write your components in an HTML file that (optionally) contains a `<style>` and `<script>` attribute describing the component's styles and behaviour. Svelte, Ractive, Vue and Polymer all follow this basic pattern.
 
 <aside>
-	<p><a href="https://svelte.technology/blog/frameworks-without-the-framework">Read the introductory blog post</a> if you're new to Svelte. Or <a href="https://twitter.com/padolsey/status/899717303234908160">read</a> <a href="https://twitter.com/sveltejs/status/901818357644701696">the</a> <a href="https://twitter.com/sveltejs/status/901818106309476352">testimonials</a>.</p>
+	<p><a href="blog/frameworks-without-the-framework">Read the introductory blog post</a> if you're new to Svelte. Or <a href="https://twitter.com/padolsey/status/899717303234908160">read</a> <a href="https://twitter.com/sveltejs/status/901818357644701696">the</a> <a href="https://twitter.com/sveltejs/status/901818106309476352">testimonials</a>.</p>
 </aside>
 
 (For the rest of this article we'll be using Svelte, obviously. But if the idea of using a template language makes you shudder — your fears are misplaced, but that's a topic for another day — then just use Vue which lets you use JSX in your SFCs.)
diff --git a/site/content/blog/2017-12-31-sapper-towards-the-ideal-web-app-framework.md b/site/content/blog/2017-12-31-sapper-towards-the-ideal-web-app-framework.md
index ff986a2258..44e2b816b3 100644
--- a/site/content/blog/2017-12-31-sapper-towards-the-ideal-web-app-framework.md
+++ b/site/content/blog/2017-12-31-sapper-towards-the-ideal-web-app-framework.md
@@ -38,7 +38,7 @@ We can do better!
 
 ## The compiler-as-framework paradigm shift
 
-[Svelte introduced a radical idea](https://svelte.technology/blog/frameworks-without-the-framework): what if your UI framework wasn't a framework at all, but a compiler that turned your components into standalone JavaScript modules? Instead of using a library like React or Vue, which knows nothing about your app and must therefore be a one-size-fits-all solution, we can ship highly-optimised vanilla JavaScript. Just the code your app needs, and without the memory and performance overhead of solutions based on a virtual DOM.
+[Svelte introduced a radical idea](blog/frameworks-without-the-framework): what if your UI framework wasn't a framework at all, but a compiler that turned your components into standalone JavaScript modules? Instead of using a library like React or Vue, which knows nothing about your app and must therefore be a one-size-fits-all solution, we can ship highly-optimised vanilla JavaScript. Just the code your app needs, and without the memory and performance overhead of solutions based on a virtual DOM.
 
 The JavaScript world is [moving towards this model](https://tomdale.net/2017/09/compilers-are-the-new-frameworks/). [Stencil](https://stenciljs.com), a Svelte-inspired framework from the Ionic team, compiles to web components. [Glimmer](https://glimmerjs.com) *doesn't* compile to standalone JavaScript (the pros and cons of which deserve a separate blog post), but the team is doing some fascinating research around compiling templates to bytecode. (React is [getting in on the action](https://twitter.com/trueadm/status/944908776896978946), though their current research focuses on optimising your JSX app code, which is arguably more similar to the ahead-of-time optimisations that Angular, Ractive and Vue have been doing for a few years.)
 
@@ -66,7 +66,7 @@ But size is only part of the story. Svelte apps are also extremely performant an
 
 The biggest drawback for many developers evaluating Sapper would be 'but I like React, and I already know how to use it', which is fair.
 
-If you're in that camp, I'd invite you to at least try alternative frameworks. You might be pleasantly surprised! The [Sapper RealWorld](https://github.com/sveltejs/realworld) implementation totals 1,201 lines of source code, compared to 2,377 for the reference implementation, because you're able to express concepts very concisely using Svelte's template syntax (which [takes all of five minutes to master](https://svelte.technology/docs#template-syntax)). You get [scoped CSS](the-zen-of-just-writing-css), with unused style removal and minification built-in, and you can use preprocessors like LESS if you want. You no longer need to use Babel. SSR is ridiculously fast, because it's just string concatenation. And we recently introduced [svelte/store](https://svelte.technology/docs#state-management), a tiny global store that synchronises state across your component hierarchy with zero boilerplate. The worst that can happen is that you'll end up feeling vindicated!
+If you're in that camp, I'd invite you to at least try alternative frameworks. You might be pleasantly surprised! The [Sapper RealWorld](https://github.com/sveltejs/realworld) implementation totals 1,201 lines of source code, compared to 2,377 for the reference implementation, because you're able to express concepts very concisely using Svelte's template syntax (which [takes all of five minutes to master](docs#template-syntax)). You get [scoped CSS](the-zen-of-just-writing-css), with unused style removal and minification built-in, and you can use preprocessors like LESS if you want. You no longer need to use Babel. SSR is ridiculously fast, because it's just string concatenation. And we recently introduced [svelte/store](docs#state-management), a tiny global store that synchronises state across your component hierarchy with zero boilerplate. The worst that can happen is that you'll end up feeling vindicated!
 
 But there are trade-offs nonetheless. Some people have a pathological aversion to any form of 'template language', and maybe that applies to you. JSX proponents will clobber you with the 'it's just JavaScript' mantra, and therein lies React's greatest strength, which is that it is infinitely flexible. That flexibility comes with its own set of trade-offs, but we're not here to discuss those.
 
diff --git a/site/content/examples/02-props/02-spread-props/App.svelte b/site/content/examples/02-props/02-spread-props/App.svelte
index f40d3b89c8..7071bdbbb7 100644
--- a/site/content/examples/02-props/02-spread-props/App.svelte
+++ b/site/content/examples/02-props/02-spread-props/App.svelte
@@ -5,7 +5,7 @@
 		name: 'svelte',
 		version: 3,
 		speed: 'blazing',
-		website: 'https://svelte.technology'
+		website: 'https://svelte.dev'
 	};
 </script>
 
diff --git a/site/content/tutorial/03-props/03-spread-props/app-a/App.svelte b/site/content/tutorial/03-props/03-spread-props/app-a/App.svelte
index 640e853c57..91ff42146d 100644
--- a/site/content/tutorial/03-props/03-spread-props/app-a/App.svelte
+++ b/site/content/tutorial/03-props/03-spread-props/app-a/App.svelte
@@ -5,7 +5,7 @@
 		name: 'svelte',
 		version: 3,
 		speed: 'blazing',
-		website: 'https://svelte.technology'
+		website: 'https://svelte.dev'
 	};
 </script>
 
diff --git a/site/content/tutorial/03-props/03-spread-props/app-b/App.svelte b/site/content/tutorial/03-props/03-spread-props/app-b/App.svelte
index f40d3b89c8..7071bdbbb7 100644
--- a/site/content/tutorial/03-props/03-spread-props/app-b/App.svelte
+++ b/site/content/tutorial/03-props/03-spread-props/app-b/App.svelte
@@ -5,7 +5,7 @@
 		name: 'svelte',
 		version: 3,
 		speed: 'blazing',
-		website: 'https://svelte.technology'
+		website: 'https://svelte.dev'
 	};
 </script>
 
diff --git a/site/package.json b/site/package.json
index 40ed8ce276..3e9926e4a9 100644
--- a/site/package.json
+++ b/site/package.json
@@ -1,5 +1,5 @@
 {
-  "name": "svelte.technology",
+  "name": "svelte.dev",
   "version": "1.0.0",
   "description": "Docs and examples for Svelte",
   "scripts": {
diff --git a/site/src/routes/blog/rss.xml.js b/site/src/routes/blog/rss.xml.js
index 5b0da33cfe..71251b1b46 100644
--- a/site/src/routes/blog/rss.xml.js
+++ b/site/src/routes/blog/rss.xml.js
@@ -13,17 +13,17 @@ const rss = `
 
 <channel>
 	<title>Svelte blog</title>
-	<link>https://svelte.technology/blog</link>
+	<link>https://svelte.dev/blog</link>
 	<description>News and information about the magical disappearing UI framework</description>
 	<image>
-		<url>https://svelte.technology/favicon.png</url>
+		<url>https://svelte.dev/favicon.png</url>
 		<title>Svelte</title>
-		<link>https://svelte.technology/blog</link>
+		<link>https://svelte.dev/blog</link>
 	</image>
 	${get_posts().map(post => `
 		<item>
 			<title>${post.metadata.title}</title>
-			<link>https://svelte.technology/blog/${post.slug}</link>
+			<link>https://svelte.dev/blog/${post.slug}</link>
 			<description>${post.metadata.description}</description>
 			<pubDate>${formatPubdate(post.metadata.pubdate)}</pubDate>
 		</item>
diff --git a/site/src/routes/gist/create.js b/site/src/routes/gist/create.js
index 1f55a51498..d93a067316 100644
--- a/site/src/routes/gist/create.js
+++ b/site/src/routes/gist/create.js
@@ -22,7 +22,7 @@ export async function post(req, res) {
 				}, null, '  ')
 			},
 			'README.md': {
-				content: `Created with [svelte.technology/repl](https://svelte.technology/repl)`
+				content: `Created with [svelte.dev/repl](https://svelte.dev/repl)`
 			}
 		};
 		components.forEach(component => {
diff --git a/site/src/server.js b/site/src/server.js
index 8a61439f5c..084b52b5b6 100644
--- a/site/src/server.js
+++ b/site/src/server.js
@@ -18,7 +18,7 @@ if (process.env.GITHUB_CLIENT_ID) {
 		clientID: process.env.GITHUB_CLIENT_ID,
 		clientSecret: process.env.GITHUB_CLIENT_SECRET,
 		callbackURL: `${process.env.BASEURL}/auth/callback`,
-		userAgent: 'svelte.technology'
+		userAgent: 'svelte.dev'
 	}, (accessToken, refreshToken, profile, callback) => {
 		return callback(null, {
 			token: accessToken,
diff --git a/test/runtime/samples/binding-audio-currenttime-duration-volume/_config.js b/test/runtime/samples/binding-audio-currenttime-duration-volume/_config.js
index 0a6754a210..d4c2b7cd0f 100644
--- a/test/runtime/samples/binding-audio-currenttime-duration-volume/_config.js
+++ b/test/runtime/samples/binding-audio-currenttime-duration-volume/_config.js
@@ -1,6 +1,6 @@
 export default {
 	// not sure if we can really test this in JSDOM. Refer to
-	// https://svelte.technology/repl?example=media-elements
+	// https://svelte.dev/repl?example=media-elements
 	// instead
 	skip: true,