UI Playbook

Dev tools

ui component documentation

SHOW HN2020

145points
33comments
#415of 3,028 in 2020
Top 14%of 2020 by points

How HN took it

RoastedHalf or more of the comments are critical

4 positive, 6 neutral or asking, 1 mixed, 12 critical, out of 23 comments about the project. Thread score -0.17.

Idea: 1 for, 4 againstExecution: 0 for, 4 againstDocs: 1 for, 1 againstDesign: 0 for, 2 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Useful wiki-style resource for common UI components

    From 2 comments
    • I feel like many commenters didn't bother to give 2 minutes to check out the site to get the gist of it. Sure, on first glance it does look like Yet Another design system or an…
      apeescape on HN
    • Very cool resource! Thanks for creating it. Accessibility is a whole beast in itself. It'd be cool to give quick suggestions on how to make the components accessible. The W3 docs…
      sankalp221 on HN
  • Good resource for learning and bookmarking

    From 2 comments
    • nice, will bookmark it for later use when there will be more content :) thanks for the effort!
      akoncius on HN
    • Nice! This is awesome!
      d0liver on HN

Objections

  • Looks like another design system, which is redundant

    From 2 comments
    • Agree with this comment. I think it is awesome that OP worked on a design system for the first time, that’s great experience to have, but it doesn’t warrant further diluting the…
      corytheboyd on HN
    • Oh, then I guess I don’t see the point? Actual design systems vary quite a bit, refer to their documentation for their exact flavor of how to implement UI correctly and eliminate…
      corytheboyd on HN
  • Site has accessibility issues itself

    From 2 comments
    • I would recommend a couple of things: Sidebar with links to headers similar to other documentation sites. And if you are going to provide insights on accessibility, which is…
      ibdf on HN
    • Install an accessibility tool such as the Wave browser extension and you can see some of the issues... eg. missing form label and contrast.
      ibdf on HN
  • Some demo elements look interactive but are not

    From 2 comments
    • You're right. Hmmm, I don't think it's very good UI design to show a UI element that turns out to be just an image or a button.
      amelius on HN
    • Not as i expected but, great work, continue, maybe in the future it doesn't just a display of only 5 different things that i already know, and one of them isn't clickable.
      mudiadamz on HN
  • Undisclosed maintainer link to Reach UI

    From 1 comment
    • Was wondering why OP only seems to recommend reach-io as examples, turns out they are a contributor. It’s all open source so like, you’re not doing anything malicious for profit…
      corytheboyd on HN

Requests

  • Add accessibility patterns for components

    From 1 comment
    • Very cool resource! Thanks for creating it. Accessibility is a whole beast in itself. It'd be cool to give quick suggestions on how to make the components accessible. The W3 docs…
      sankalp221 on HN
  • Add sidebar navigation with header links

    From 1 comment
    • I would recommend a couple of things: Sidebar with links to headers similar to other documentation sites. And if you are going to provide insights on accessibility, which is…
      ibdf on HN
  • Add more components such as spinbox or number input

    From 2 comments

Questions

  • How does it differ from Storybook

    From 2 comments
    • What are the main differences between this and storybook?
      rebelrexx858 on HN
    • This is a website detailing various UI components whereas storybook is a development tool where you can manipulate and view components you are building locally (although some…
      lajr on HN
  • Should it collaborate with open-ui

    From 1 comment
    • This reminds me of open-ui [1]. The goal of that project is also to tackle fragmentation and allow interoperability between component frameworks and design systems. How does UI…
      miguelsm on HN
  • Why adapt an existing design system instead of building from scratch

    From 1 comment
    • What's your general thought on adapting one of the bigger design systems with thousands of hours of improvement & polishing vs building one from scratch? I do think there is need…
      masonhensley on HN

Alternatives named

  • Storybook

    From 1 comment
  • Existing corporate design systems

    From 1 comment
    • What's your general thought on adapting one of the bigger design systems with thousands of hours of improvement & polishing vs building one from scratch? I do think there is need…
      masonhensley on HN
  • open-ui

    From 1 comment
    • This reminds me of open-ui [1]. The goal of that project is also to tackle fragmentation and allow interoperability between component frameworks and design systems. How does UI…
      miguelsm on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/23916842)