Critique of Component Library: Color Variables and Documentation Issues
The color variables are HORRIBLY thought out. I鈥檓 having to go back and fix them which is tedious and defeats the point of a headless block library which I am supposed to be able to use in conjunction with my global color variables for faster development. The button variants are laughably bad with how they are integrated with the color variables. They are literally inaccessible from a color standpoint just using the default implementations. Was there zero Q/A done before release? These are day 1 issues that a junior can fix. You also have zero written documentation on the color variables. Everything I have had to comment myself to understand it. The library鈥檚 layout for its components is great but I am shocked how incompetently designed the color variables and button colors are in general. You also have differently structured import statements for each component, making fixing the file paths to go from your obfuscated node module button component to my fixed manual one even more tedious. I鈥檓 sure you never intended anyone to actually download these in bulk and attempt to use all 1400 components.. that鈥檚 probably why you are heavily obfuscating all of your code both in your node modules distribution and on your website鈥檚 front-end. It was pretty trivial to remove all of the spans you wrap around your code in the HTML, but come on, really guys? You surely know you can render different components based on logged in state, why not give logged-in paid users the ability to get the components via API/programmatically? Leave the obfuscation for the free tier/not logged-in users. One of your big selling points is how big your library is, yet you actively attempt to restrict users to only manually copy and pasting? You started out so well and I was so hyped to use this library, then I realize I have to copy/paste each one individually, all of the color variables are fucked under the hood, the global container horizontal padding is a pain to fix globally and requires manual revisions if you want to customize, there is zero documentation on some of the most crucial aspects, and if you do want to fix the UI elements manually, the import paths are all structured slightly differently, meaning you have to do 4-5 replace searches for each UI primitive, instead of just one. Which adds up when you are having to fix the colors of EVERY UI primitive, since they were fucked from the start. You literally have 4-5 of the colors in your example tailwind config that are flat-out not used in a single component, and another 2-3 color variables are only used in like 50 components combined. Meaning you have 1250-1300 components integrated with like 3-4 color variables. Great for wire framing in just a couple of colors, horrible for building a production site with color variables as the basis. Add on top of that the 40-50 components that are plain inaccessible and show errors when you click them in the dashboard. Sigh, yet another component library fallen to enshittification. Here鈥檚 a hint, the AAA gaming studio model of releasing alpha versions into production and having your users be paid testers, is not a winning strategy to emulate. I am more than happy to be a paid Q/A tester if you offer, but unpaid you can forget it. Putting this out there so anyone else wanting to use this library in production can understand the work that will need to go into it before it鈥檚 ready. It鈥檚 definitely a quality library, but there鈥檚 clearly some decisions being made behind the scenes hampering it. Whether from the CEO/founders or someone else (maybe P.E. backers?). These fixes are too trivial to assume they come from incompetence, there is something else causing them.
