Managing icon component sizes
It's time to retire that icon wrapper component
Alice Packard is a design operations practitioner who loves supporting her team. This journal is where she documents her career journey, writes about things she's made, and experiences she's had.
It's time to retire that icon wrapper component
mostly boring, unsexy features and capabilities for Figma Design
SVGs are the way
and what to do instead
Designers strive to make usable products. And components are themselves tiny products... let's make 'em usable!
Variables, variants, component swapping, and component properties all offer different advantages. Choosing the right feature is key to building a strong component library.
Chrome, Safari, and Firefox, for both Windows and Mac, all utilizing Figma's auto-layout feature
Let's look at the tradeoffs between file performance and component management and maintence that come with this method of building components
tired: light/dark, wired: density
one component per page is not the only (or best) solution
It doesn't matter! Use both! You can have it all!
"it works fine on the canvas, but not when it's nested inside another component?!"
Collapsing SVGs into one layer is expensive, risky, and makes for a more fragile icon collection
reject the allure of the crystal ball, embrace not knowing, and know peace
And thumbs, chevrons, trend lines...
there's two different workarounds!
Why swapping arrow-right for arrow-down still shows an arrow pointing to the right
Let's get your file memory back.
alt title: how to make sense of variable collections in Figma
It turns out layers and large variant sets aren't the only things eating up file memeory
A workaround for managing prototype-ready materials in your library
According to Figma’s documentation this isn’t possible, but I’ve found a way to get around it. No plugin required.
Here's a hint: space between is an overrideable attribute...
Because "just practice" and "learn flexbox" aren't good enough.
Just because they've fallen out of favor with design system folks, doesn't mean they're not useful!
For when the default 800x450 just doesn't cut it
Spice up your FigJam communication game
The concept is useful, but I have beef with the execution.
How the new features and enhancements affect my past blog posts
Checkboxes, yes. Radios, no.
reduce memory usage, improve component usability, and a third thing!
wish me luck!
And understanding how they relate to the other 6 types will unlock a whole new level of workflow precision
You're already use first type... but what about the other 6?
Spoiler: almost everything you make should be a component... almost...
Upgrading from willy-nilly class names to B-E-M naming conventions
No matter how much time you're spending on a wireframe, you need it to effectively communicate an idea. How do you optimize for fidelity?
If Bon Appetit asked me to do a "Making Perfect" for job searching.
The techniques are: "basic", "starter-kit", and "slot"
Confidently choose a building method that will benefit you in the future