2 files changed, 19 insertions, 53 deletions

diff --git a/docs/integration.md b/docs/integration.md
index d186704..4de4953 100644
--- a/docs/integration.md
+++ b/docs/integration.md
@@ -6,7 +6,7 @@ A Ferdi recipe is basically nothing else than a node module and is currently ini
 
 > ℹ️ New to Ferdi recipes and Electron? Then we recommend you read Jake Lee's ["Super simple guide to adding a new Ferdi service recipe"](https://blog.jakelee.co.uk/super-simple-guide-to-adding-a-new-ferdi-service-recipe/) which gives you an easy step-by-step guide on how to create and publish your recipe!
 
-> ℹ️ If you have any problems packaging your recipes, if you are inexperienced with the tools used or have any other problems, we are here to help! Just open a new issue at https://github.com/getferdi/recipes/issues/new and we can help you develop, test and publish your recipe and can package the recipe for you if you don't feel like you are able to.
+> ℹ️ If you have any problems packaging your recipes, if you are inexperienced with the tools used or have any other problems, we are here to help! Just open a new issue at https://github.com/getferdi/recipes/issues/new and we can help you develop, test and publish your recipe
 
 > If you want to update an existing recipe, please refer to [updating.md](https://github.com/getferdi/recipes/blob/master/docs/updating.md) instead
 
@@ -25,25 +25,26 @@ A Ferdi recipe is basically nothing else than a node module and is currently ini
   - [Publishing](#publishing)
 
 ## Preparing
-Before you can begin, you should have [NodeJS](http://nodejs.org/) installed and should be familiar with using npm, specifically "npm install" and "npm run".
+You should have basic knowledge of JavaScript - don't worry, you'll really only need some basic commands as we've already prepared the complicated stuff for you.
 
-You should also have basic knowledge of JavaScript - don't worry, you'll really only need some basic commands as we've already prepared the complicated stuff for you.
+We have also created a nice script that already does 50% of the work for you - yay 🎉. If you want to use this script, please make sure you have NodeJS installed on your system.
 
 ## Create a recipe
-1. Clone this repository. You can do this by running `git clone https://github.com/getferdi/recipes.git` in your terminal or by downloading the repository from <https://github.com/getferdi/recipes/archive/master.zip>.
-2. Install its dependencies via the terminal:
+1. Fork this repository on GitHub. You can do this by clicking the "Fork" button in the top right corner
+2. Clone your forked repository. Normally, you can do this by running `git clone https://github.com/<Your GitHub Username>/recipes.git` in your terminal. You may also use a Git GUI or the GitHub Website for this.
+2. (Optional, if you want to use our creation script) Install its dependencies via the terminal:
 ```Bash
-cd scripts/
 npm install
 ```
 3. You can now run our automatic recipe wizard that creates and opens the new recipe for you:
 ```Bash
-# Make sure you are still in the scripts/ folder
+# Make sure you are still in the repository's folder
 npm run create "Service Name"
 ```
 Replace `Service Name` with the name of your service, e.g. `npm run create "Google Hangouts"`.
 This command will automatically create the development recipe in the correct folder, prepares it for your service and opens the new recipe in your file explorer or Finder.
 4. Reload Ferdi (`CMD/CTRL + SHIFT + R`) in order for it to register the new recipe
+5. You can now develop your recipe as described below. Please continue down below with "[Publishing](#Publishing)" after you are done creating your recipe.
 
 ## Recipe structure
 Every recipe needs a specific file structure in order to work as a Ferdi recipe
@@ -179,21 +180,6 @@ In order to debug your service integration, open Ferdi and use the shortcut `Cmd
 ## Publishing
 Ferdi uses its recipe repository at <https://github.com/getferdi/recipes> to publish recipes to all clients.
 
-> Our scripts are designed to work best on Linux and macOS systems. If you want to use these scripts on Windows, you may need to use [WSL](https://docs.microsoft.com/en-US/windows/wsl/install-win10) in order for the scripts to function correctly. If you have problems with packaging, please open a new issue at https://github.com/getferdi/recipes/issues/new and we can package your recipe for you.
-
-To add your own recipe to the repository:
-- If you already uploaded the recipe to GitHub:
-  1. Fork https://github.com/getferdi/recipes and clone it to your computer
-  2. Open a terminal in the `scripts/` folder of that repository
-  3. Run `npm install` to install all dependencies
-  4. Run `npm run github [GitHub URL]`, e.g. `npm run github https://github.com/vantezzen/franz-recipe-standardnotes`, to add your new recipe
-  5. Create a PR to <https://github.com/getferdi/recipes> with your new changes
-
-- If you don't have it uploaded it GitHub:
-  ℹ️ We recommend uploading your recipes to GitHub before adding them to provide a platform for users to report issues.
-  1. Fork https://github.com/getferdi/recipes and clone it to your computer
-  2. Copy your recipe files into `scripts/recipe_src`
-  3. Open a terminal at `scripts/`
-  4. Run `npm install` to install all dependencies
-  5. Run `npm run package` to package your new recipe
-  6. Create a PR to <https://github.com/getferdi/recipes> with your new changes
+Publishing your recipes to Ferdi is super easy! When you used our recipe creation script, we have created a folder for your recipe inside Ferdi's internal folders (the one that got automatically opened after you ran our script).
+
+Simply copy that whole folder into the repositories "recipes" folder. You'll now need to push your changes to Git and create a Pull Request from your fork repository to our repository using the GitHub website.
\ No newline at end of file
diff --git a/docs/updating.md b/docs/updating.md
index ac2e126..000b362 100644
--- a/docs/updating.md
+++ b/docs/updating.md
@@ -2,16 +2,6 @@
 
 If you want to improve or update an existing recipe, please follow this guide.
 
-Please **do not** simply change files inside `uncompressed` - Ferdi only uses the packaged archives, the uncompressed files are only to improve accessibility of the repository.
-
-## 0. Find the recipe ID of the recipe you want to update
-
-Before you can start updating the recipe, you'll need to know its internal ID. The ID is a string of lowercase letters and hyphens that Ferdi uses to store and manage them.
-
-To find the recipe ID, you can search <https://github.com/getferdi/recipes/blob/master/all.json> for the recipe you want to edit.
-
-In the rest of this guide, always replace "&lt;recipe id>" with the ID of the recipe you want to edit.
-
 ## 1. Implement your updates
 
 We highly suggest that you implement and test your updates to the recipe inside Ferdi before implementing them into the recipe repository. This will save you time on debugging and repackaging the recipe later.
@@ -21,32 +11,22 @@ You can find the recipe source Ferdi uses at:
   * Windows: `%appdata%/Ferdi/recipes/<recipe id>/`
   * Linux: `~/.config/Ferdi/recipes/<recipe id>`
 
+> If you can't find the recipe's folder, please make sure that you have created a service inside Ferdi with that recipe - otherwise Ferdi will not load it into the folder
+
 After changing the files in that folder, you can reload the service inside Ferdi using `CTRL/CMD + R`.
 
 ## 2. Setting up the recipe repository
 
-- Fork https://github.com/getferdi/recipes and clone it to your computer
-- Open a terminal in the `scripts/` folder of that repository
-- Run `npm install` to install all dependencies
-
-This will setup the repository so that you can work on updating it.
+Simply fork https://github.com/getferdi/recipes. You may also want to clone the repository to your computer to edit it locally.
 
-## 3. Loading and updating the recipe
+## 3. Updating the recipe inside the repository
 
-Again, please **do not** edit any of the files located inside the `uncompressed` folder! Before editing, you'll need to "load" the recipe you want to edit using
-```JavaScript
-npm run load <recipe id>
-```
-(e.g. `npm run load gmail`)
-
-Your recipe is now loaded into `scripts/recipe_src`. You can now make changes to the files **in that folder*.
+Simply add your changes to the recipe inside this repository.
 
 ## 4. Updating the version number
 
-In order for Ferdi to update its recipe, you'll need to bump its version number. Increase the `version` inside `scripts/recipe_src/package.json`.
-
-## 5. Re-packaging the recipe
+This might be the __most important step__ of this guide. You'll need to increase the version number inside recipe's `package.json`.
 
-You can now run `npm run package` to repackage your updated files. Your changes will be automatically copied into the recipe source at `uncompressed` and compressed into `archives/<recipe id>.tar.gz` - no need to update anything manually!
+Ferdi uses this version to determine if it should update the local copy of the recipe. If you do not increase the version number, no Ferdi user will get your updated recipe 😔
 
-## 6. Commit your changes and create a PR to <https://github.com/getferdi/recipes>
+## 5. Commit your changes and create a PR to <https://github.com/getferdi/recipes>