31–36 of 36 posts
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 great, make sure your site is also accessible.
Care to elaborate which parts weren’t accessible for ya? Thanks.
I mean, the 5th one isn't even available yet, just a teaser. :)
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 alternative to Storybook, but in fact it's something else. This is sort of a wiki for common UI components, i.e., there's information on when to use them, how to implement them, common gotchas, and so on. Since using a 3rd party design system…
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 alternative to Storybook, but in fact it's something else. This is sort of a wiki for common UI components, i.e., there's information on when to use them, how to implement them, common gotchas, and so on. Since using a 3rd party design system…
I think author wouldn't have this problem if they wrote "Best practices for common UI components" instead of "The documented collection of UI components" as the header.
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!