Consolidate and/or document deployment tasks

[contolini]

There are several tasks with similar names (ship, release, deploy) in the gruntfile. Is this cruft from when we were beta testing the site? Can we fold them into one or two tasks? If we can't, can someone document their purposes in the README?

[himedlooff]

It looks like build and release are the two main tasks. ship is used in conjunction with both of those.

default = build + ship
deploy = release + ship

One of the more obvious differences between build and release is that release is more picky about what it copies into dist. This is cool because you can merge files into the repo without having them go live. If you want something to go live you need to update the copy:release task.

It would be nice if the build server used grunt instead of grunt deploy so that the build server shows all files, not just the ones going live.

[ascott1]

Good sniffin' @himedlooff. This is definitely cruft from the early days and could use some clean up.

[cfarm]

This process would be more straightforward if we could keep master as the deployable production-ready branch and could build feature branches to see our changes and share them.

[cfarm]

@contolini is there a standard set of grunt tasks we can be using here for the different build steps? something that works across projects?