feedback'd:

- added link to @kentcdodd's contributing how-to course
- moved checklist to the top

Author: benmosher

CONTRIBUTING.md

@@ -3,6 +3,20 @@
 Thanks for your interest in helping out! Here are a **few** _weird_ tricks to
 ~~cut your mortgage in half~~ maximize the global net efficiency of your efforts!
 
+## TL;DR: Checklist
+
+When opening an [issue](#issues):
+- [ ] search open/closed issues
+- [ ] discuss bug/enhancement in new or old issue
+
+[PR](#prs) time:
+- [ ] write tests
+- [ ] implement feature/fix bug
+- [ ] update docs
+- [ ] make a note in change log
+
+Remember, you don't need to do it all yourself; any of these are helpful! 😎
+
 ## Issues
 
 ### Search open + closed issues for similar cases.
@@ -32,7 +46,11 @@ This is a helpful contribution all by itself. Thanks!
 ## PRs
 
 If you would like to implement something, firstly: thanks! Community contributions
-are a magical thing. Like Redux or the flux capacitor, they make open source possible.
+are a magical thing. Like Redux or [the flux capacitor](https://youtu.be/SR5BfQ4rEqQ?t=2m25s),
+they make open source possible.
+
+**Working on your first Pull Request?**
+You can learn how from this _free_ series [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github).
 
 Here are some things to keep in mind when working on a PR:
 
@@ -50,7 +68,7 @@ jumping-off point for a core contributor or even another PR to continue what you
 For enhancements to rules, please update the docs in `docs/rules` matching the rule
 filename from `src/rules`.
 
-Also, take a quick look at the rule summary in README.md in case it could use tweaking,
+Also, take a quick look at the rule summary in [README.md] in case it could use tweaking,
 or add a line if you've implemented a new rule.
 
 Bugfixes may not warrant docs changes, though it's worth skimming the existing
@@ -66,19 +84,6 @@ Note also that the change log can't magically link back to Github entities (i.e.
 issues, users) or rules; there are a handful of footnote URL definitions at the bottom.
 You may need to add one or more URL if you've square-bracketed any such items.
 
-## Checklist
-
-- [ ] search open/closed issues
-- [ ] discuss bug/enhancement in new or old issue
-
-PR time:
-- [ ] write tests
-- [ ] implement feature/fix bug
-- [ ] update docs
-- [ ] make a note in change log
-
-Remember, you don't need to do it all yourself; any of these are helpful! 😎
-
 ## Code of Conduct
 
 This is not so much a set of guidelines as a reference for what I hope may become
@@ -107,3 +112,5 @@ If we can all get together behind the common goal of embracing empathy, everythi
 
 Thanks for help from http://mozillascience.github.io/working-open-workshop/contributing/
 for inspiration before I wrote this. --ben
+
+[README.md]: ./README.md