Adam Aho

Initial iteration of Menu component done for Winnie React. I am really really liking some of the abstractions Winnie affords. You can dive into the tools at any level and make them what you want. Winnie React just represents one way to do things.

I'm convinced that polymorphism in components is not needed when you have the right style abstractions. Need an anchor that looks like a button? In Winnie, just add `data-component="button"` to it, and now it looks like a button.

Winnie strikes a nice balance with the support of tailwind. Only works in v4 though thanks to the css only config. Get all the power of Winnie CSS with tailwind.

winnie-ui.com/css/docs/sta...

Cooking something new for Winnie.

PS. In the world of React components, React Aria really needs more love. It's the only unstyled library with almost everything you need. With the addition of Autocomplete, I think it might get even closer

winnie provides entry for developers on on different levels. Want total control over the system? use only Winnie css and integrate with any framework you want. Next step up is React. I’m currently working on a wrapper of Winnie components in react with the help of react aria.

Or finally, you can use Winnie Themes. A thin layer on top of the React components that applies the colors and opinions for you, all you need to do is choose your accent color, radius and scale.

winnie provides entry for developers on on different levels. Want total control over the system? use only Winnie css and integrate with any framework you want. Next step up is React. I’m currently working on a wrapper of Winnie components in react with the help of react aria.

Astro 5 update for the Winnie docs was pretty seamless. Although, I think I need to wait to upgrade to react 19. At least for now.

Excited to see how @base-ui.com implemented css transition support into their components. This is a super underrated feature imo. For the Winnie showcase, I spent a lot of time fine-tuning the layout sidebar component to support transitions.

One thing I have noticed about other demo apps in the wild is that noneo of them support writes. They are all read only. To me I feel like that doesnt convey the value enough. I want to be able to use something real, even if just for 5 mins.

So for Winnie, I have decided to make the showcase app support mutations. Local only purely with local storage. That way people can see what it feels like to use an application built with Winnie for real, instead of just clicking around in read only mode

In my experience pure css thrives in design systems and libraries. Often times these use cases require many variants, sizes, colors, etc. something I find to be hard to read and quite verbose in other utility class type libraries.

However, I think utility classes have a place in application code. Where you use them to sprinkle styles on top of already existing components from your design system. This tends to be the balance I strike between pure css and something like tailwind.

just released a new component in winnie! its an opinionated layout component that you can use for your next application. While it works perfectly with just css and html, you can take it a step further with js. winnie-ui.com/css/docs/com...

react-aria has been my go to recently. It feels like Devon has thought of everything. I just finished implementing an accessible drag handle with the help of useMove