diff --git a/examples/guides/svelte/.gitignore b/examples/guides/svelte/.gitignore
new file mode 100644
index 00000000..da93220b
--- /dev/null
+++ b/examples/guides/svelte/.gitignore
@@ -0,0 +1,4 @@
+/node_modules/
+/public/build/
+
+.DS_Store
diff --git a/examples/guides/svelte/README.md b/examples/guides/svelte/README.md
new file mode 100644
index 00000000..22f7e0f7
--- /dev/null
+++ b/examples/guides/svelte/README.md
@@ -0,0 +1,147 @@
+## 1. Create a new Svelte project
+
+Let's start by creating a new Svelte project called `tailwindcss-svelte` with the following command:
+
+```sh
+npx degit sveltejs/template tailwindcss-svelte
+```
+
+Once the template is cloned, we can move into our new directory and install the dependencies with:
+
+```sh
+cd tailwindcss-svelte && npm install
+```
+
+At this point, you should be able to start your app with `npm run dev` and see it in action at `localhost:5000` 👍
+
+## 2. Adding Tailwind CSS as a dependency
+
+Let's now bring in Tailwind CSS. We'll also install a few other packages like `autoprefixer`, `postcss-cli` and `concurrently`:
+
+```sh
+npm install tailwindcss autoprefixer postcss-cli concurrently
+```
+
+## 3. Generate Tailwind and PostCSS config files
+
+Let's now generate default `tailwind.config.js` and `postcss.config.js` files:
+
+```sh
+npx tailwindcss init -p
+```
+
+## 4. Create a CSS file with the `@tailwind` directives
+
+Inside the `public` directory, let's create a new file called `tailwind.css`. In there, we'll have our 3 `@tailwind` directives:
+
+```css
+/* public/tailwind.css */
+@tailwind base;
+@tailwind components;
+@tailwind utilities;
+```
+
+## 5. Update the scripts in `package.json` to run our CSS through PostCSS
+
+First, let's add a `watch:tailwind` script that will take the `public/tailwind.css` file as an input, run it through PostCSS, write the output in a file called `public/tailwind-output.css`, and watch for changes in the input file:
+
+```javascript
+// package.json
+{
+ // ...,
+ "scripts" : {
+ "watch:tailwind": "postcss public/tailwind.css -o public/tailwind-output.css -w",
+ // ...
+ }
+}
+```
+
+Let's also add a `build:tailwind` script that does the same, but with `NODE_ENV` set to `production`, so that it can be used to purged unused styles. This one doesn't need the "watch" flag, since it will likely only be run once when building for production.
+
+```javascript
+// package.json
+{
+ // ...,
+ "scripts" : {
+ "build:tailwind": "NODE_ENV=production postcss public/tailwind.css -o public/tailwind-output.css",
+ // ...
+ }
+}
+```
+
+Finally, we'll update the `dev` script to _concurrently_ start rollup **and** run the `watch:tailwind` script:
+
+```javascript
+// package.json
+{
+ // ...,
+ "scripts" : {
+ "dev": "concurrently \"rollup -c -w\" \"yarn run watch:tailwind\"",
+ // ...
+ }
+}
+```
+
+## 6. Link the output CSS file in our HTML template
+
+In our `watch:tailwind` and `build:tailwind` scripts, we've told PostCSS to put our compiled Tailiwnd CSS in `public/tailwind-output.css`. For this to become useful, we need to add a `` tag in our `index.html` file that references that CSS file:
+
+```diff
+// public/index.html
+
+
+
+
+
+
+ Svelte app
+
+
+
+
++
+
+
+
+
+
+
+
+```
+
+## 7. Play with Svelte and Tailwind!
+
+To verify that Tailwind CSS is now working in our Svelte app, let's modify the `src/App.svelte` file.
+
+Let's replace the entire file with the following:
+
+```html
+
+
+