I love the craftsmanship of UI design. Especially the intricacies of what could go into a Design System. The way I approached learning this craft was, after getting some bare minimum basics down, I jumped to reading Design Systems. Not just theory, but very importantly drilling deep down into the vast abyss of the Design system documentation published by various companies.
Also, reverse engineering UI kits and replicating the components with their properties has been super useful and has been by far, most influential in me acquiring some chops for the craft. This is an underrated practice. UI Prep, Untitled UI and Once UI have been some kits that have been very helpful.
All that said, I decided to create my own UI kit (Tenet UI). I think knowing how to create components is one thing but creating a UI kit is a whole new challenge. Not just that, I want to create it as close to being a Design System, with design tokens and robust documentation in place.
I have lots more ideas that I want to execute with Tenet UI. I want it to be more than just a UI kit. But, without jumping the gun and looking too much into the future, I’ll let the project pan out on its own.
Meanwhile here’s a sneak peek into how Tenet UI is shaping up! 👇