4 ms·
Show HN: Designer Lynx – curated links to useful UI design resources
- redbergy 9y agoCool 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! Video in case you can't recreate: https://streamable.com/mwee8 https://streamable.com/mwee8
- lucasverra 9y agoYou've added value to my life. Thank you for that Somewhere (icons?) I'd add http://fontawesome.io/ http://fontawesome.io/
- StevieA 9y agoGood tip, will add tonight.
- akoncius 9y agoreally nice, thanks! sent to my GF to keep an eye on this website :)
- dylz 9y agoNice site. Consider clearly displaying that you are using affiliate links. Was somewhat of a shock when I got a ublock screen on click.
- StevieA 9y agoGood point, will do. It's only on the books, was debating whether to do it or not but if it helps a bit with hosting costs I thought, 'why not'.
- lucasverra 9y agomake it explicit enough "if you buy i get some $$$ to pay for servers"and you should be fine
- dylz 9y agoYou may want to check out section 5 in https://affiliate-program.amazon.com/help/operating/agreement https://affiliate-program.amazon.com/help/operating/agreemen... too. Hope things go well.
- derekmcloughlin 9y agoSorry, I refuse to read white text on a black background.
- Raphmedia 9y agoI 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.
- StevieA 9y agoHi there, 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.
- Raphmedia 9y agoThe fact that Karla (your body font) gets blurry at 13px makes it worst that it should be. https://snag.gy/Z5Aibp.jpg 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)
- nategri 9y agoI think a lot of people here are going to read 'Lynx' and suffer a namespace collision.
- deleted 9y ago[deleted]
- RickS 9y agoThis 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: https://github.com/brillout/awesome-react-components https://github.com/brillout/awesome-react-components
- StevieA 9y agoYeah, when I bunged all the content in, I was concerned it was all too much to parse easily. I think for V2 I'll split each section into a separate page and present the links in format similar to your example.