Cool site! The hovers for me are a little jolting (all of the cells flash when I mouse over one). Safari 10.1.2 on OS X 10.12.6. Normally I would ignore something like this but since it's a site focused on design/UX I figured you'd probably want to know. Bookmarked, nice work!
I don't think that this comment should be downvoted.
Web Content Accessibility Guidelines (AAA) recommends text of that contrast ratio (#969696 on #1d1d1d) to be at least 18pt.
What may sometimes seem like nitpicking can actually be your users not being able to see your content at all or without feeling nauseous and dizzy.
Increasing the card's text size to 18px from the current 13px doesn't even break the layout. People these days should know better than to use print sized text on the web.
Agreed that the text could be a little larger. Due to the amount of content I wanted to try and keep things compact, but as stated in another comment above, it could be easier to parse.
The text does pass accessibly standards though, #A4A4A4 on #1D1D1D gets a AA rating on small text and AA rating on large text.
But duly noted your comments and I shall rethink the layout for V2.
The fact that Karla (your body font) gets blurry at 13px makes it worst that it should be. https://snag.gy/Z5Aibp.jpg (left: karla, right: tahoma).
That being said, a good rule of thumb is to consider "small text" to mean 16px and "large text" to mean 18px bold / 24px regular. (Since the guidelines are in pt and not px)
This is a really great list, but tbh the site is enormously wide, the text is small, and there are no images. This would be far more parseable in the form of a github readme, since it lends itself to categorized lists like this:
18 comments
[ 3.9 ms ] story [ 14.6 ms ] threadVideo in case you can't recreate: https://streamable.com/mwee8
Somewhere (icons?) I'd add http://fontawesome.io/
Web Content Accessibility Guidelines (AAA) recommends text of that contrast ratio (#969696 on #1d1d1d) to be at least 18pt.
What may sometimes seem like nitpicking can actually be your users not being able to see your content at all or without feeling nauseous and dizzy.
Increasing the card's text size to 18px from the current 13px doesn't even break the layout. People these days should know better than to use print sized text on the web.
Agreed that the text could be a little larger. Due to the amount of content I wanted to try and keep things compact, but as stated in another comment above, it could be easier to parse.
The text does pass accessibly standards though, #A4A4A4 on #1D1D1D gets a AA rating on small text and AA rating on large text.
But duly noted your comments and I shall rethink the layout for V2.
That being said, a good rule of thumb is to consider "small text" to mean 16px and "large text" to mean 18px bold / 24px regular. (Since the guidelines are in pt and not px)
https://github.com/brillout/awesome-react-components
I think for V2 I'll split each section into a separate page and present the links in format similar to your example.