[WIP] Port to ES2016, Refactor & Enhancements

.babelrc

@@ -0,0 +1,5 @@
+{
+  "presets": ["es2015-node5", "stage-0"],
+  "plugins": ["add-module-exports", "transform-runtime"],
+  "sourceMaps": "inline"
+}

.gitignore

@@ -1,4 +1,16 @@
 .DS_Store
 node_modules
 coverage
-src
+lib
+logs
+*.log
+npm-debug.log*
+pids
+*.pid
+*.seed
+lib-cov
+.grunt
+.lock-wscript
+build/Release
+.nyc_output
+test/fixtures/*/public

.istanbul.yml

@@ -0,0 +1,2 @@
+instrumentation:
+  root: src

.npmignore

@@ -1,4 +1,9 @@
 test
 src
 .travis.yml
+.istanbul.yml
+.editorconfig
+.babelrc
+wallaby.js
 Makefile
+.nyc_output

.travis.yml

@@ -1,6 +1,9 @@
 language: node_js
 node_js:
-  - "0.10"
+  - "5"
 after_script:
   - npm run coveralls
 sudo: false
+cache:
+  directories:
+    - node_modules

Makefile

@@ -1,11 +1,20 @@
 build:
-	cp -R lib src
-	./node_modules/.bin/coffee -c lib
-	find lib -iname "*.coffee" -exec rm '{}' ';'
+	npm run build
 
-unbuild:
-	rm -rf lib
-	mv src lib
+coverage::
+	npm run coverage
 
 coveralls:
-	NODE_ENV=test istanbul cover ./node_modules/mocha/bin/_mocha --report lcovonly -- -R spec && cat ./coverage/lcov.info | ./node_modules/coveralls/bin/coveralls.js && rm -rf ./coverage
+	npm run coveralls
+
+release:
+	npm run release
+
+lint:
+	npm run lint
+
+debug-test:
+	npm run debug-test
+
+test::
+	npm test

contributing.md

@@ -1,5 +1,5 @@
 
-# Contributing to Roots-contentful
+# Contributing to `roots-contentful`
 
 Hello there! First of all, thanks for being interested in this project and helping out. We all think you are awesome, and by contributing to open source projects, you are making the world a better place. That being said, there are a few ways to make the process of contributing code to this project smoother, detailed below:
 
@@ -14,15 +14,85 @@ If you are opening an issue about a bug, make sure that you include clear steps
 - Run `npm install`
 - Put in work
 
-### Testing
+### `pre-commit` Linting
 
-This project is constantly evolving, and to ensure that things are secure and working for everyone, we need to have tests. If you are adding a new feature, please make sure to add a test for it. The test suite for this project uses [mocha](http://visionmedia.github.io/mocha/) and [should](https://github.com/visionmedia/should.js/)/
+Provided dependencies are installed, `git commit` will
+not work unless this project passes a linting check.
 
-To run the test suite, make sure you have installed mocha (`npm install mocha -g`), then you can use the `npm test` or simply `mocha` command to run the tests.
+### Build Commands
+
+> **Note:** if your environment does not support `make` utilities,
+> replace `make` with `npm run` when you type a build command.
+
+#### Testing
+
+This project is constantly evolving, and to ensure that things are secure and working for everyone, we need to have tests. If you are adding a new feature, please make sure to add a test for it. The test suite for this project uses [AVA](https://github.com/sindresorhus/ava).
+
+To lint the source:
+
+```shell
+$ make lint
+```
+
+To lint the source and run the tests:
+
+```shell
+$ make test
+```
+
+By default, tests will run concurrently/in parallel. When debugging, this can sometimes lead to unwanted behavior. For this reason, there is a `debug-test` command that will fail as soon as the first test fails, run tests serially, enable more verbose output and also log any HTTP requests:
+
+```shell
+$ make debug-test
+```
+
+To create a coverage report:
+
+```shell
+$ make coverage
+```
+
+To feed a coverage report to coveralls:
+
+```shell
+$ make coveralls
+```
+
+#### Building
+
+> **Note:** Building the project will not work if any of the tests fail.
+
+Building involves compiling the ES2016 syntax down to
+regular ES5 using [Babel](http://babeljs.io). This command will run the tests - on success it will then compile the contents of `src/` into `lib/`.
+
+```shell
+$ make build
+```
+
+#### Publishing to NPM
+
+This command will lint the project files, run the tests, build the project, publish the build to NPM and then perform a `git push --follow-tags`.
+
+```shell
+$ make release
+```
+
+A typical publish workflow might look something like this:
+
+```shell
+$ git checkout Fix/bug-fix
+# add some code...
+$ git add .
+$ git commit -m "fixed a bug"
+$ git checkout master
+$ git merge Fix/bug-fix
+$ npm version patch
+$ make release
+```
 
 ### Code Style
 
-To keep a consistant coding style in the project, we're using [Polar Mobile's guide](https://github.com/polarmobile/coffeescript-style-guide), with one difference begin that much of this project uses `under_scores` rather than `camelCase` for variable naming. For any inline documentation in the code, we're using [JSDoc](http://usejsdoc.org/).
+To keep a consistent coding style in the project, we're using [JavaScript Standard Style](https://github.com/feross/standard), with one difference being that much of this project uses `under_scores` rather than `camelCase` for variable naming. For any inline documentation in the code, we're using [JSDoc](http://usejsdoc.org/).
 
 ### Commit Cleanliness