Last week, my friend Eric Bailey shared some thoughts on Design Systems on Bluesky…
I'm by no means an expert on design systems, but I've been at companies with one, companies without one, and companies that built one but struggled to get people to use it. Where I often see design systems fail is when they're overly prescriptive. Typically, one of two things happens…
The most effective design systems I've seen are a bit like Legos…
That last part is, in my opinion, critical. Some Design Systems try to actively prevent developers from writing CSS. They're basically just "proprietary Tailwind/Bootstrap." But the goal of a Design System isn't to prevent developers from ever writing CSS. It's to…
There were always be things that the system doesn't cover yet that need building. Providing a way for your developers to extend the existing system to build those things (ideally faster and easier) makes them more likely to use it, and provides useful stuff for you to funnel back into the official system. Like this? A Go Make Things membership is the best way to support my work and help me create more free content. Cheers, Want to share this with others or read it later? View it in a browser. |
0 Komentar untuk "[Go Make Things] Design Systems and Legos"