Designer-Oriented Styles

James Kyle:

Components are a designer’s bread and butter. Designers have been building design systems with some model of “component” for a really long time. As the web has matured, from Atomic Design to Sketch Symbols, “components” (in some form or another) have asserted themselves as a best practice for web designers ...

Designers don’t care about selectors or #TheCascade. They might make use of it since it’s available, but #TheCascade never comes up in the design thought process.

(Okay okay... most designers. You're special. But we both knew that already.)

I think James makes strong points here. I'm, predictably, in the camp in which I like CSS. I don't find it particularly hard or troublesome. Yet, I don't think in CSS when designing. Much easier to think (and work) in components, nesting them as needed. If the developer flow matched that, that's cool.

I also agree with Sarah Federman who chimed in on Twitter:

It seems a bit premature to look at the current landscape of component CSS tooling at say that it's designer-friendly.

The whole conversation is worth reading, ending with:

Tooling that treats component design as an interface with the code is where it's at/going to be. Hopefully, designers will be more empowered to create component styles when we can meet them closer to their comfort zone.

How Do You Hire a Designer?

My friend Jeff just asked me this question. He was looking for a designer for a one-off graphic design job. He had the project all scoped out. He just didn't know how to do it. He's not a fool; he web searched around for stuff, but what you find doing that is a confusing mess with plenty of results that don't feel right.

I figured I'd document that journey here, and contrast it hiring an electrician. A trite comparison, perhaps, but as the light switch in my bathroom doesn't work right now and I'm actually in the process of hiring an electrician, it seems apt.