##PROTIP: README Love
READMEs are AWESOME. They are one of the best things you can add to a repo, (other than quality code), to make it look professional.
####Things that make a README great:
- A link to the production site on heroku
- A screenshot (or a few) of what the app does (This is especially important if you don't have the production app up and running yet)
- Directions on how to clone or fork the repo and run it locally (explain it like you're explaining things to a totally new programmer)
- Directions on how to run the tests
- Directions on how to seed the database (if relevant)
As projects grow, these instructions are vital to getting open source contributions...
But most importantly for students, READMEs are vital for helping classmates contribute, giving the repos a professional look and feel, and for impressing future employers.
You never know when a potential employer will be looking at your Github, so make your repos looks great.
####Examples of Good READMEs
- Katrina Owen is the queen of documentation.
- Apollo.io
- I assure you, the website no longer works, but it LOOKS like it does on the repo
- Jeff Casimir is pretty good at docs too
- Jekyll
- You don't have to cram all the documentation in one file, check out the Jekyll repo!
####Markdown References
- Markdown Basics
- Github Flavored Markdown
- Get a goodmarkdown editor! Not sure what's hip now, but I've used Mou
- Check out Recordit.co
- Here's an example
When does this come up? If you're working in a branch and add a hardcoded link in your readme to something in the repo, when you merge back to master the image link will no longer work. Here are instructions