Documentation work items

This issue is here to track the progress of updating, trimming down, and adding to the current Zen Audio Player docs & wiki pages. The four files/sections for docs are as follows: CONTRIBUTING.md, ISSUE_TEMPLATE.md, PULL_REQUEST_TEMPLATE.md, and the Wiki pages.
The main tasks that we are prospectively looking to address are:

• Decide what amount of content to move from markdown files (Contributing, Issues, PRs), to Wiki pages (I think the issue & PR templates are too verbose, we should have a simpler checklist for both, ideally under 5 items)
• How to test things locally (WAMP, MAMP, XAMPP) vs. opening the index.html file in a browser (we should recomment just running npm install then npm start for "running" the site, then npm test to run the tests - the main requirement here is Node.js 4.0+)
• How to write tests & run tests
• What are our code conventions/style? (a .jshintrc would help a bunch here) (see .eslintrc.json, coordinate those rules with the eslint docs and we could make something more human readable on the wiki)
• How to install dependencies (frontend & test) (npm install for "running" and testing, bower (frontend) depdendencies are checked in, but in order to update I believe you run bower update --save <package-name>)
• What to look for in a successful/unsuccessful work session (nothing specific here, but the goal is always to minimize the diff, ie: don't go refactoring unless it's necessary because the diff becomes difficult to review)
• Tools (why did we pick certain things? bower/node.js/specific dependencies/gitter/travis CI) - (there are some notes in @shakeelmohamed's blog post ping him for any additional info)
• What is the contributing process like? (@shakeelmohamed's code review on the PR, contributor updates PR, repeat until everyone is satisfied)
• How to get started quickly as a newbie
• Branching model (basically master is locked down, and can only be pushed to via a PR that passes code review)

Hey @shakeelmohamed, let me know if you'd like to revise anything here. I based this off the original list in the other issue. Perhaps we can also close issue #49 once this one looks good to go.

[shakeelmohamed]

I've left some comments bold inline above to help whoever ends up doing these tasks, thanks for triaging @josectello!

@shakeelmohamed Are we thinking of adding any future content (from the list) to only the Wiki pages or do you think any of these items will require PR's - or the creation of another markdown file?

[shakeelmohamed]

@josectello aside from the first item on the list, I think the others make sense being on the wiki. What do you think?

@shakeelmohamed I like the idea of having denser content in the Wiki, but I often find myself (when looking through open source repos) completely forgetting that a Wiki tab even exists.

What about inserting a link someplace on the main README.md to the Wiki?

[shakeelmohamed]

@josectello that makes sense, we can add a link to the wiki at the end of the contributing section of the README 👍

[FleetAdmiral]

Is the discussion still on for this?

[shakeelmohamed]

@FleetAdmiral Definitely, I'd like to see these items done one at a time FYI

[FleetAdmiral]

@shakeelmohamed Cool with me, can i pick any item too look into or is there an order you'd like to follow?

[shakeelmohamed]

@FleetAdmiral you can start with any of them