Update CONTRIBUTING.md

Author: jmdobry

.github/CONTRIBUTING.md

@@ -1,37 +1,86 @@
 # Contributing to js-data-mongodb
 
-[Read the general Contributing Guide](http://js-data.io/docs/contributing).
+Dear contributor,
 
+**Thank you!** Projects like this are successful because of you!
+
+## Getting started
+
+1. Read the the general [JSData Contributing Guide](http://js-data.io/docs/contributing)
+1. To report a bug or request a feature, please [open an issue](https://github.com/js-data/js-data-mongodb/issues/new)
+  * Be sure to search the existing issues to prevent duplication
+  * Give your issue a short but descriptive title
+  * For bug reports, please include all steps to reproduce the error
+  * For feature requests, please include details of your use case
+1. To improve to the JSData + MongoDB tutorial, go to [js-data.io/v3.0/docs/js-data-mongodb](http://www.js-data.io/v3.0/docs/js-data-mongodb) and click "Suggest Edits"
+1. To improve the API Reference Documentation, write a test, fix a bug, or add a feature:
+  1. Create a fork of github.com/js-data/js-data-mongodb. [Click here](https://github.com/js-data/js-data-mongodb#fork-destination-box) to do so now.
+  1. Clone your fork:
+
+      ```
+      git clone git@github.com:YOUR_USERNAME/js-data-mongodb.git
+      ```
+  1. Change directory to `js-data-mongodb`:
+
+      ```
+      cd js-data-mongodb
+      ```
+  1. Install development dependencies
+
+      ```
+      npm install js-data@rc bson mongodb
+      npm install
+      ```
+1. To just update API Reference Documentation, make changes to the [JSDoc](http://usejsdoc.org/) comments in the source code. To regenerate the API documentation:
+
+    ```
+    npm run doc
+    ```
+
+    You can find the regenerated API Reference Documentation in the `doc/` folder.
+1. To write a test, fix a bug, or add a feature, make your changes to files in the `src/` and `test/` folders.
+1. To run the tests, first make sure MongoDB is running in another terminal window:
+
+    ```
+    mongod --config /path/to/mongod.conf
+    ```
+1. Now run the tests:
+
+    ```
+    npm test
+    ```
+    
 ## Project structure
 
+* `coverage/` - Code coverage report produced by `npm test`
 * `dist/` - Contains final build files for distribution
 * `doc/` - Output folder for JSDocs
 * `src/` - Project source code
 * `test/` - Project tests
 
-## Clone, build & test
-
-1. `clone git@github.com:js-data/js-data-mongodb.git`
-1. `cd js-data-mongodb`
-1. `npm install`
-1. `npm run build` - Lint and build distribution files
-1. `npm run mocha` - Run tests (RethinkDB must be running)
-
 ## To cut a release
 
-1. Checkout master
+1. `git checkout master`
 1. Bump version in `package.json` appropriately
 1. Update `CHANGELOG.md` appropriately
-1. Run `npm run release`
-1. Commit and push changes
-1. Checkout `release`, merge `master` into `release`
-1. Run `npm run release` again
-1. Commit and push changes
-1. Make a GitHub release
+1. `npm run release`
+1. Commit and push changes (message should be something like "Prepare for VERSION")
+1. `git checkout release`
+1. `git merge master`
+1. `npm run release`
+1. Commit and push changes (message should be something like "VERSION")
+1. [Make a new GitHub release](https://github.com/js-data/js-data-mongodb/releases/new)
   - tag from `release` branch
   - set tag name to version
   - set release name to version
   - set release body to changelog entry for the version
 1. `npm publish .`
+1. `git checkout gh-pages`
+1. `cp -r doc/js-data-mongodb/VERSION VERSION`
+1. `cp -r doc/js-data-mongodb/VERSION latest`
+1. `git add -A`
+1. `git commit -m "VERSION"`
+1. `git push -u origin gh-pages`
+1. `git checkout master`
 
-See also [Community & Support](http://js-data.io/docs/community).
+See also [JSData Community & Support](http://js-data.io/docs/community).