Live data from Hacker News

Show HN: UI Playbook – A documented collection of UI components

uiplaybook.dev

1–10 of 36 posts

Re: Show HN: UI Playbook – A documented collection of UI components

#2
Hey!

After my first experience with design systems, I decided to kickstart a project called UI Playbook which is my attempt to document common UI components, their functionality, best practices, accessibility requirements, and examples.

If at least one person finds this useful — it's a win!

Re: Show HN: UI Playbook – A documented collection of UI components

#4

What are the main differences between this and storybook?

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 people end up hosting a static version of their storybook somewhere).

Re: Show HN: UI Playbook – A documented collection of UI components

#6

Hey! After my first experience with design systems, I decided to kickstart a project called UI Playbook which is my attempt to document common UI components, their functionality, best practices, accessibility requirements, and examples. If at least one person finds this useful — it's a win!

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 for a common vernacular in these components, however I think that too often teams start from scratch when they could pull something off the shelf, and swap out some colors.

List of corporate sponsored design systems: https://designsystemsrepo.com/design-systems/

Re: Show HN: UI Playbook – A documented collection of UI components

#9

Hey! After my first experience with design systems, I decided to kickstart a project called UI Playbook which is my attempt to document common UI components, their functionality, best practices, accessibility requirements, and examples. If at least one person finds this useful — it's a win!

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 for a common vernacular in these components, however I think that too often teams start from scratch when they could pull something off the shelf, and swap out some colors. List of corporate sponsored design systems: https://designsystemsrep…

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 market with another unfinished system.
Post reply on HN