Comply with "sindresorhus/awesome" requirements

[robatwilliams]

https://github.com/sindresorhus/awesome/blob/master/pull_request_template.md

• [x] Has been around for at least 30 days.
  That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
• [x] It's the result of hard work and the best I could possibly produce.
• [x] Non-generated Markdown file in a GitHub repo.
• [x] Includes a succinct description of the project/theme at the top of the readme. (Example)
• [x] The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• [x] Not a duplicate.
• [x] Only has awesome items. Awesome lists are curations of the best, not everything.
• [ ] Includes a project logo/illustration whenever possible.
  • [ ] Either centered, fullwidth, or placed at the top-right of the readme. (Example)
  • [ ] The image should link to the project website or any relevant website.
  • [ ] The image should be high-DPI. Set it to maximum half the width of the original image.
• [x] Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
• [x] Includes the Awesome badge.
  • [x] Should be placed on the right side of the readme heading.
    • Can be placed centered if the list has a centered graphics header.
  • [x] Should link back to this list.
• [x] Has a Table of Contents section.
  • [x] Should be named Contents, not Table of Contents.
  • [x] Should be the first section in the list.
  • [x] Should only have one level of nested lists, preferably none.
• [x] Has an appropriate license.
  • [x] That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
  • [x] WTFPL and Unlicense are not acceptable licenses.
  • [x] If you use a license badge, it should be SVG, not PNG.
• [x] Has contribution guidelines.
  • [x] The file should be named contributing.md. Casing is up to you.
• [x] Has consistent formatting and proper spelling/grammar.
  • [x] The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
  • [x] The description starts with an uppercase character and ends with a period.
  • [x] Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• [x] Doesn't include a Travis badge.
  You can still use Travis for list linting, but the badge has no value in the readme.

[robatwilliams]

There are some remaining possible issues. If solving them makes the list less useful, I won't solve them.

1. Status section
2. Good to know section
3. Candidate devices section
4. Ideas section
5. Placeholder sections
6. Some sections with intros (where useful), others without
7. Source names in brackets between some links and descriptions
8. Secondary links within some descriptions

[robatwilliams]

There have been some updates to the requirements since I opened this issue: https://github.com/sindresorhus/awesome/commits/master/pull_request_template.md

https://github.com/sindresorhus/awesome/commit/e53741c4850efb8117a6ffdf8918399c34bd64b1#diff-081a901bcd6f61bef29110a1bc408818 - in compliance.

https://github.com/sindresorhus/awesome/commit/efc69ed013896c466df6e3ec89f0753eb92edc02#diff-081a901bcd6f61bef29110a1bc408818 - in compliance except:

• [ ] Run awesome-lint on your list and fix the reported issues.

https://github.com/sindresorhus/awesome/commit/a4dc681a0a33668ebb0af7f2a4cd89bb0e3318d9#diff-081a901bcd6f61bef29110a1bc408818 - in compliance

[justinclift]

sindresorhus/awesome is an extreme mess. Is it really worth putting effort into meeting their guidelines?

[robatwilliams]

Closing; there's little value in full compliance - the list is tidy and organised as it is, and the deviations from requirements are with good reason which add value.