From a356c022123aba6df2f63194f7b8633217b62110 Mon Sep 17 00:00:00 2001 From: Rich Harris Date: Wed, 4 Nov 2020 00:49:01 -0500 Subject: [PATCH] replace video link with an embed --- .../2020-11-03-whats-the-deal-with-sveltekit.md | 12 +++++++++++- site/src/routes/blog/[slug].svelte | 13 ------------- 2 files changed, 11 insertions(+), 14 deletions(-) diff --git a/site/content/blog/2020-11-03-whats-the-deal-with-sveltekit.md b/site/content/blog/2020-11-03-whats-the-deal-with-sveltekit.md index acaa38beb1..1be7a63f78 100644 --- a/site/content/blog/2020-11-03-whats-the-deal-with-sveltekit.md +++ b/site/content/blog/2020-11-03-whats-the-deal-with-sveltekit.md @@ -7,12 +7,22 @@ authorURL: https://twitter.com/rich_harris -If you attended [Svelte Summit](https://sveltesummit.com/) last month you may have seen my talk, [Futuristic Web Development](https://www.youtube.com/watch?v=qSfdtmcZ4d0), in which I finally tackled one of the most frequently asked questions about Svelte: when will Sapper reach version 1.0? +If you attended [Svelte Summit](https://sveltesummit.com/) last month you may have seen my talk, Futuristic Web Development, in which I finally tackled one of the most frequently asked questions about Svelte: when will Sapper reach version 1.0? The answer: never. This was slightly tongue-in-cheek — as the talk explains, it's really more of a rewrite of Sapper coupled with a rebrand — but it raised a lot of new questions from the community, and it's time we offered a bit more clarity on what you can expect from Sapper's successor, SvelteKit. +
+
+
+ +
+ +
'Futuristic Web Development' from Svelte Summit
+
+
+ ## What's Sapper? diff --git a/site/src/routes/blog/[slug].svelte b/site/src/routes/blog/[slug].svelte index b97b5ef136..236d649d56 100644 --- a/site/src/routes/blog/[slug].svelte +++ b/site/src/routes/blog/[slug].svelte @@ -172,17 +172,4 @@ margin: 2em auto; } } - - /* @media (min-width: 1460px) { - .post :global(iframe) { - width: 1360px; - margin: 2em -280px; - } - } - - @media (min-height: 800px) { - .post :global(iframe) { - height: 640px; - } - } */