4/ Status Annotations, built by @negativespaceca, allows you to indicate the status of your designs to avoid ambiguity when collaborating with your team.
5/ Quantizer, built by @aswellasyouare, allows you to organize a selection of elements into a grid of your choosing by specifying number of columns as well as column and row gaps.
Continuing on all things design systems! Did you know Figma curates designsystems.com? There is a wealth of content here written by the community. Here are some of my favorite articles 👇
2/ Icons are a key part of most design systems, @bonniekatewolf takes you through lots of practical tips about pixel perfectness to creating size-specific icons. designsystems.com/iconography-gu…
This is a story of a Figma bug that wasn’t a bug at all.
In November of 2019, one of our users reported this: ⁝ MW
In short, pressing Shift+2 using one key worked, but pressing Shift+2 using the numeric keypad key didn’t.
Curiously, the bug only happened on Windows, and not on a Mac.
Turns out this bug goes back all the way to… 1977.
This was the time when IBM, the #1 computer maker of that time, continued their attempts to conquer the burgeoning small, personal computer market. (Before, most of their computers looked like the one below.)
It’s the coldest of takes that as a designer you have to learn to constantly switch between thinking of big things and considering details. ⁝ MW
The former is crucial, but the details can make or break a product. On the other hand, details can also suffocate you – there are endless small fixes, torrents of bugs, and infinite polish that could be applied to anything… but there is never infinite time.
As a result, you need to develop a sense of which details matter, and which not… and constantly seek input on your calibration.