Goals for "Build Tools" folder

[JordanMartinez]

This folder should accomplish the following:

• Explain the differences between Bower and psc-package
• Document the CLI options for the most popular tools: purs, pulp, psc-package. (Others may be added over time like purs-loader)
• Document a typical workflow from project start to finish (creation, fast-feedback development, initial publishing, 'bump' publishing)

[JordanMartinez]

This issue is largely done. The only thing I have left to verify is publishing, which is hard to verify without doing it and uploading spam. Also, I'm not sure whether one can publish docs to Pursuit if one does not use bower as they somewhat refer to this issue in the last paragraph of this section.

[JordanMartinez]

Due to this article on Haskell's 4 workflows and since Justin Woo uses Emacs for his workflow process AFAIK, it might make more sense to update the build tools to use that text editor instead of Atom.

[JordanMartinez]

Document purescript/psc-package#43

[JordanMartinez]

psc-package cannot be used to publish docs to Pursuit. However, I wonder if that's still important if one can just generate the docs for all used packages in one's project locally. Or, if such a thing could be done directly in the package-set repo...

[JordanMartinez]

I'm going to say this issue has largely been accomplished. Tasks that haven't been addressed should be opened in separate issues.