🌶️🌶️ HOT TAKE🌶️🌶️
Your users of #DesignSystems are not the users of your application, they are the beneficiaries.
The devs implementing the system are your users. The worse that UX is, the less likely your design system will successfully be implemented.
@stuffbreaker Is this a "Hot Take"? I thought this was _just the facts_. ™️
If there is a developer between you and an end user your user is the developer. Make their job easier, bring #a11y to the surface, bring #performance to the surface, bring #usability to the surface by making it such that what is easy is what is right and what is right will serve their use (maybe the end user) in was that they would likely not have done without your #designSystem.
@westbrook I felt like this was common sense, but that doesn't seem to be the case.
I have seen components and themes with very complicated setup processes and configurations and intricate decision trees to help "guide" devs to the right tool. These are all red flags for me. 🚩
@stuffbreaker Yes, common doesn't seem so correlative to sense these days. In so many things... 🤦♂️
There's also components that lock you into specific build processes or frameworks, what a shame. 🫨
Or worse, frameworks or tools that lock you out if you don't. 😱
I've been tracking your work on #wcToolkit and definitely see tools like that as making it look sillier and sillier when those teams make those sorts of decisions. 🙇
Burton Smith
westbrook