rthrblck/arthurblackdesign — pull request #5 by christianbundy (2014-09-24 05:08:31+00:00)
Title: Update config files so that it works on a clean install

I just wanted to throw together a pull request to make sure that everything works how it should on a clean install. Just to summarize what I did:

* I added `npm-debug.log` to the `.gitignore` since it's generated when NPM crashes, and shouldn't be part of the version history.
* I added your repository to the `package.json` so that NPM would stop bitching about it. I didn't do anything else, but you can see [the rest of the options](http://browsenpm.org/package.json) if you ever want to fill out package.json completely.
* I added [scripts](https://github.com/christianbundy/arthurblackdesign/blob/3443557afbbcd412aba86344481d7b881452503f/package.json#L8-12) to `package.json` so that you don't need to install Grunt globally to get everything up and running. This doesn't break the way you currently do things, but adds an option to use the `npm` tool that ships with Node instead of installing `grunt-cli`. Both `npm start` and `npm test` are [default scripts](https://www.npmjs.org/doc/misc/npm-scripts.html) that NPM knows how to deal with, but any custom ones (like "deploy") have to be run with `npm run deploy`.
* I added a quick-n-dirty README (with [README Boilerplate](https://github.com/fraction/readme-boilerplate)) with how everything works right now.

Eventually it might be cool to add a "Do you want to deploy?" [prompt](https://github.com/dylang/grunt-prompt) to the `test` Grunt task (so you don't have to have a separate `grunt deploy`/`npm run deploy`), but it works how it should right now.

P.S. It looks like there's some weird Gruntfile stuff going on with a clean install, but I'm assuming that will be solved by you reconfiguring your tasks to have separate folders. The commits in this pull request deal *only* with your config files, so it shouldn't affect anything else.