Bias in Design Systems - bencallahan.com
Thoughtful analysis from Ben (as always).
I like the idea of “design bugs”:
Every two weeks or so, a group of designers would get together for a couple of hours to fix what we called “design bugs.” These were things that didn’t hinder functionality and wouldn’t have been filed as an engineering bug, but were places where we were using an old component, an existing one incorrectly, or a one-off alteration.
Thoughtful analysis from Ben (as always).
Whenever I confront a design system problem, I ask myself this one question that guides the way: “What would HTML do?”
HTML is the ultimate composable language. With just a few elements shuffled together you can create wildly different interfaces. And that’s really where all the power from HTML comes up: everything has one job, does it really well (ideally), which makes the possible options almost infinite.
Design systems should hope for the same.
Okay, if you weren’t already excited for Patterns Day, get a load of what Rich is going to be talking about!
You’ve got your ticket, right?
Here’s the transcript of a great talk by Amy on the realities of working on design systems.
Here’s an aggregator of components from multiple design systems.
There’s probably a Pace Layer analogy in here somewhere.
A problem shared is a problem halved. And the web has a big problem with awful overlays.
A presentation at An Event Apart San Francisco 2019
From pattern portfolios to Fractal.
Gotta keep ‘em separated.