Beef dat README [WIP - not ready to merge yet]

[jglovier]

Getting setup to work on code is difficult with the existing state of the README. Let's flesh it out better to make working on the front-end much easier for anyone who wants to do so. ✨ 💥 ⚡

RENDERED

❤️ 🍰 📝 🍰 ❤️

Addresses #2

[jkleinsc]

Any reason you did this as a PR instead of directly committing yourself?

[jglovier]

Any reason you did this as a PR instead of directly committing yourself?

Yes, because I want to teach you to use GitHub flow. 😸 We should never commit directly to master, that's only for code cowboys.

Seriously though, feature branching and pull requests allows for us to get the most benefit out of the collaborative process, forcing us to put multiple eyes on changes and to keep everyone aware of where things are headed, etc.

Plus, once we have CI setup, that will allow us to see if our changes break anything before merging them in (Travis FTW). I'd be happy to explain more about how to squeeze the most benefits out of this workflow, but here's a great articles that sum it up better than I will:

• Understanding the GitHub Flow
• GitHub Flow
• GitHub Flow in the Browser

[jglovier]

Any reason you did this as a PR instead of directly committing yourself?

Also, just because you can doesn't mean you should. Just because we are technically maintainers doesn't mean we shouldn't act like contributors. Behaving like contributors (at least workflow-wise) will give us a mentality that allows us to optimize for contributors. If you want to build a thriving OSS community around this project, we need to act like a group of contributors rather than a group of maintainers. ⚡