From ca060be80e0d67f079610263f5229656c6ea6891 Mon Sep 17 00:00:00 2001
From: Rich Harris <richard.a.harris@gmail.com>
Date: Wed, 26 Dec 2018 14:53:54 -0500
Subject: [PATCH] add css-in-js post

---
 .../blog/2018-12-26-svelte-css-in-js.md       | 29 +++++++++++++++++++
 site/src/routes/blog/[slug].html              | 21 ++++++++++++++
 2 files changed, 50 insertions(+)
 create mode 100644 site/content/blog/2018-12-26-svelte-css-in-js.md

diff --git a/site/content/blog/2018-12-26-svelte-css-in-js.md b/site/content/blog/2018-12-26-svelte-css-in-js.md
new file mode 100644
index 0000000000..2d36e2c71d
--- /dev/null
+++ b/site/content/blog/2018-12-26-svelte-css-in-js.md
@@ -0,0 +1,29 @@
+---
+title: Using CSS-in-JS with Svelte
+description: You don't need to, but you can
+pubdate: 2018-12-26
+author: Rich Harris
+authorURL: https://twitter.com/Rich_Harris
+---
+
+CSS is a core part of any web app. By extension, a UI framework that doesn't have a built-in way to add styles to your components is unfinished.
+
+That's why Svelte allows you to add CSS in a component's `<style>` tag. Co-locating your CSS with your markup means we can [solve the biggest problems developers face when writing CSS](/blog/the-zen-of-just-writing-css) without introducing new ones, all while providing a rather nice development experience.
+
+But Svelte's style handling does have some limitations. It's too difficult to share styles between components, or apply app-level optimisations. These are areas we plan to address in future versions, but in the meantime if you need those things you can use any framework-agnostic CSS-in-JS library.
+
+
+## For example
+
+Here, we're using [Aphrodite](https://github.com/Khan/aphrodite) to generate scoped class names that can be used across multiple components:
+
+<iframe
+	title="Aphrodite example"
+	src="/repl/embed?gist=01345cf1c2c9ec0dfd617c2e2adb7bf7"
+	scrolling="no"
+></iframe>
+
+It's important to note that most CSS-in-JS libraries have a runtime library, and many don't support statically extracting styles out into a separate <code>.css</code> file at build time (which is essential for the best performance). You should therefore only use CSS-in-JS if it's necessary for your application!
+
+Note that you can mix-and-match — you can still use Svelte's built-in CSS handling alongside a CSS-in-JS library.
+
diff --git a/site/src/routes/blog/[slug].html b/site/src/routes/blog/[slug].html
index 2d27e0bd2d..2b04108d81 100644
--- a/site/src/routes/blog/[slug].html
+++ b/site/src/routes/blog/[slug].html
@@ -82,4 +82,25 @@
 		color: var(--second);
 		z-index: 2;
 	}
+
+	.post :global(iframe) {
+		width: 100%;
+		height: 420px;
+		margin: 2em 0;
+		border-radius: var(--border-r);
+		border: 0.8rem solid var(--second);
+	}
+
+	@media (min-width: 910px) {
+		.post :global(iframe) {
+			width: calc(100vw - 2 * var(--side-nav));
+			margin: 2em calc(400px + var(--side-nav) - 50vw);
+		}
+	}
+
+	@media (min-height: 800px) {
+		.post :global(iframe) {
+			height: 640px;
+		}
+	}
 </style>
\ No newline at end of file