SVGs are the way

and what to do instead

It doesn't matter! Use both! You can have it all!

It's time to retire that icon wrapper component

Collapsing SVGs into one layer is expensive, risky, and makes for a more fragile icon collection

one component per page is not the only (or best) solution

tired: light/dark, wired: density

Why swapping arrow-right for arrow-down still shows an arrow pointing to the right

And thumbs, chevrons, trend lines...

there's two different workarounds!

It turns out layers and large variant sets aren't the only things eating up file memeory

reduce memory usage, improve component usability, and a third thing!

A workaround for managing prototype-ready materials in your library

Checkboxes, yes. Radios, no.

alt title: how to make sense of variable collections in Figma

wish me luck!

How the new features and enhancements affect my past blog posts

The concept is useful, but I have beef with the execution.

Here's a hint: space between is an overrideable attribute...

Spice up your FigJam communication game

reject the allure of the crystal ball, embrace not knowing, and know peace

Let's get your file memory back.

Because "just practice" and "learn flexbox" aren't good enough.

For when the default 800x450 just doesn't cut it

Just because they've fallen out of favor with design system folks, doesn't mean they're not useful!

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?

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.

"it works fine on the canvas, but not when it's nested inside another component?!"

The techniques are: "basic", "starter-kit", and "slot"

Confidently choose a building method that will benefit you in the future

Let's look at the tradeoffs between file performance and component management and maintence that come with this method of building components

Spoiler: almost everything you make should be a component... almost...

According to Figma’s documentation this isn’t possible, but I’ve found a way to get around it. No plugin required.

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?

Chrome, Safari, and Firefox, for both Windows and Mac, all utilizing Figma's auto-layout feature

Upgrading from willy-nilly class names to B-E-M naming conventions

If Bon Appetit asked me to do a "Making Perfect" for job searching.