Design Systems for Developers VS UI Playbook

Design Systems for Developers mentions (4)

• How to avoid magic numbers?

  There's a whole idea of design system in frontend development, you can learn that more here: https://storybook.js.org/tutorials/design-systems-for-developers/ (I actually haven't read them, it's just one of the first result google gave me, but I know and use storybook.js and I can recommend their tool for creating a robust design system. Source: about 1 year ago

• Career options - Junior dev/Senior designer

  You basically work in a team of developers and designers that maintain a catalog of components for a company. Your team would make sure all the components are accessible, consistent across all platforms, and are being used correctly within your applications. Here is a deep dive for developers on how these systems are used, built, and maintained. Source: about 2 years ago

• Creating a design system using Vanilla Extract CSS

  ℹ️ This article goes deep into design system foundational topics like tokens, themes, variants. If you aren’t sure what some of these are, I’d check out a guide or tutorial that covers those. - Source: dev.to / about 2 years ago

• Storybook gives you unit tests, but for UI

  Storybook is a really good tool for building design systems. Ideally you'll want to distribute them library through npm. Here's a tutorial for it: https://storybook.js.org/tutorials/design-systems-for-developers/. Source: almost 3 years ago

UI Playbook mentions (0)