Jan Toman prepared a small file covers kit with several styles and unique waves-like artwork for each color. He also shared a few principles behind them.
Jan Toman wrote a guide for using Figma branches to improve the reliability of UI components. His approach of always using branches for design system contributions and creating a set of visual regression tests is similar to the best practices in the development world and should really help with making a design system more robust.
Jan Toman with a thread of different ways this plugin can be used to automate routine operations of maintaining a design library, removing the need to use checklists, and increasing consistency along the way.
Finally found some time to play with Automator plugin from @tricycleai. This thing can replace so many checklists (!!!), helping us to scale a consistency in our whole Figma library. No matter who is contributing.— Jan Toman (@HonzaTmn) November 6, 2021
🧵 Thread with examples ⤵️
A nice tip to UI kit maintainers from Jan Toman.
💡 A small usability tip for @figmadesign UI kit maintainers:— Jan Toman (@HonzaTmn) October 15, 2021
Add the component name to the component description. It's especially useful when the component name is longer than ~10 characters. pic.twitter.com/gawuvNle6X
If you liked Jan Toman’s talk at Schema, check out this one as well.
Jan Toman (see his Schema talk above) with a few recommendations for design system maintainers.
A simple tip for UI kit maintainers in @figmadesign:— Jan Toman (@HonzaTmn) October 3, 2021
- Release changes in smaller batches
- Add a detailed description of what was changed
- (Optional) Reassure consumers that nothing will break
Write changelogs. Small things like this matter. pic.twitter.com/J6kA16pj1f
Jan Toman, Productboard. “Not sure where to start? Get your libraries off the ground by learning how to craft UI kits that designers will love using. We'll dive into building flexible components, aligning their API with code, and dealing with changes as the design system evolves.”