Add Matt's blog post

Author: danthareja

README.md

@@ -30,35 +30,35 @@ You can do this one of two ways:
   1. In the menu that appears, choose `Other` for the `Application type`.
   1. Give it any name you like and click `Create`.
   1. Finally, download your credentials using the `Download as JSON` button to the right.
-    - Save these credentials to a location of your choosing; `~/Downloads` is fine.
+    * Save these credentials to a location of your choosing; `~/Downloads` is fine.
   1. You may close the Developer Console window.
 
 #### 1.2 Independent Developer Console Project
 
 1. Create a new Dev Console Project
   1. Use [this link](https://console.developers.google.com/start/api?id=drive&credential=client_key) to create the project. It will auto-activate the Google Drive API.
-    - If you have multiple Google Accounts, append `&authuser=1` to the end of the url to choose which account to login with. Note that `authuser` is zero-indexed.
+    * If you have multiple Google Accounts, append `&authuser=1` to the end of the url to choose which account to login with. Note that `authuser` is zero-indexed.
   1. Make sure `Create a New Project` is selected and hit `Continue`.
   1. Once the project has been created, click `Go to Credentials`.
 1. Acquire Google Drive Client Secret Credentials
   1. Select `Add credentials`, choose the `OAuth 2.0 client ID` type
   1. Click `Configure Consent Screen`.
   1. Select your email address from the dropdown and assign your add-on a Project Name.
-    - This can always be changed later.
+    * This can always be changed later.
   1. `Save` your Consent Screen
   1. In the menu that appears, choose `Other` for the `Application type`.
   1. Give it any name you like and click `Create`.
   1. Finally, download your credentials using the `Download as JSON` button to the right.
-    - Save these credentials to a location of your choosing; `~/Downloads` is fine.
+    * Save these credentials to a location of your choosing; `~/Downloads` is fine.
   1. You may close the Developer Console window.
-    - To return to this project later, select `Resources` > `Developer Console Project` while editing your script. Then click the link at the top of the dialog to open the Developer Console with this project selected.
+    * To return to this project later, select `Resources` > `Developer Console Project` while editing your script. Then click the link at the top of the dialog to open the Developer Console with this project selected.
 
 ### 2. Authenticate `gapps`
 
 This process will set up Google Drive authentication to allow uploading and importing of the Apps Script project.
 
 1. Run `gapps auth path/to/client_secret_abcd.json`
-  - i.e. `gapps auth ~/Downloads/client_secret_1234567890-abcd.apps.googleusercontent.com.json`
+  * i.e. `gapps auth ~/Downloads/client_secret_1234567890-abcd.apps.googleusercontent.com.json`
 1. Follow the directions by clicking on the link generated by the script.
 1. After you're successfully authenticated, feel free to delete the `client_secret.json` credentials file.
 
@@ -72,21 +72,21 @@ This proces will create `gapps.config.json` and a sub-directory where all Apps S
 
 1. Navigate to your Apps Script project from Google Drive (must be a [standalone script](https://developers.google.com/apps-script/guides/standalone))
 1. Get your project ID from the address bar, located after `/d/` and before `/edit`.
-  - For example, '//script.google.com/a/google.com/d/__abc123-xyz098__/edit?usp=drive_web'
+  * For example, '//script.google.com/a/google.com/d/__abc123-xyz098__/edit?usp=drive_web'
 1. Navigate to a directory where your Apps Script project will live
 1. Run `gapps init <fileId>` within your project directory.
-  - For example, `gapps init abc123-xyz098`
+  * For example, `gapps init abc123-xyz098`
 
 #### 3.2 A new Apps Script project
 
 1. Head to [https://script.google.com](https://script.google.com) and create a new blank project.
 1. Save the mostly empty project and give it a name.
-  - Saving is important; the project is not in your Google Drive until it is saved.
+  * Saving is important; the project is not in your Google Drive until it is saved.
 1. Get your project ID from the address bar, located after `/d/` and before `/edit`.
-  - For example, '//script.google.com/a/google.com/d/__abc123-xyz098__/edit?usp=drive_web'
+  * For example, '//script.google.com/a/google.com/d/__abc123-xyz098__/edit?usp=drive_web'
 1. Navigate to a directory where your Apps Script project will live
 1. Run `gapps init <fileId>` within your project directory. 
-  - For example, `gapps init abc123-xyz098`
+  * For example, `gapps init abc123-xyz098`
 
 
 ### 4. Develop locally
@@ -100,14 +100,7 @@ Run `gapps upload` from within your project directory. You should then be able t
 
 ## Best Practices
 
-- Only upload to Google Drive and never edit files in the web IDE
-  - This way the true state of the code is locally or in git and you'll never
-    need to deal with issues where the states locally and remotely are not in
-    sync.
-  - You also get the benefits of structuring code within directories
-  - Individual developers can have separate devevelopment Apps Script projects,
-    and the overall solution can have shared test, ua-testing, and production
-    targets all with different settings.
+Check out Matt Hessinger's blog post: [Advanced development process with apps](http://googledevelopers.blogspot.com/2015/12/advanced-development-process-with-apps.html)
 
 ## Docs
 

package.json

@@ -1,7 +1,7 @@
 {
   "name": "node-google-apps-script",
   "version": "1.1.3",
-  "description": "The easiest way to manage your Google Apps Script project from the command line",
+  "description": "The easiest way to develop Google Apps Script projects",
   "repository": {
     "type": "git",
     "url": "https://github.com/danthareja/node-google-apps-script.git"