coolcss VS stitches

To add onto this, CUBE has taken inspiration from Tailwind among many other things. And it's not alone... cool.css, Chakra-UI, and Stitches all take ideas from Tailwind because utility classes + design tokens are a very attractive abstraction while not being as heavy-handed as entire CSS frameworks without familiar lower-level conveniences. Maybe there're even more frameworks I don't know of.

Nicely done. I like this approach and rationale. I've taken a similar approach to custom CSS for sites, but have never taking the time to abstract it as is done here.

While I liked the overview on the home page, it took me a bit to find the actual CSS. A kind of 'component library' demo page (like the https://coolcss.dev/kitchen-sink/, but with the CSS class info displayed rather than using the dev-tools to explore) would be nice.

For now, just digging through this dir will give you a good idea of what's here: https://github.com/peruvianidol/coolcss/tree/main/_src/sass

Also, I can't decide if have the "oo" in "cool" stand for "Utility" is genius or madness.

Over the past few years, I've worked with React apps utilising various CSS-in-JS libraries, starting with styled-components, transitioning through emotion, Theme UI, and finally Stitches. I've also integrated MUI, Mantine, and Chakra in numerous client projects.

Radix has some great ideas that challenge the way components are usually built. I'd love to use it, but am somewhat burned by how Stitches stopped being maintained due to the changes in React 18. Context: https://github.com/stitchesjs/stitches/discussions/1149#disc...

To be clear, it's not so much that they decided to not spend time, energy and money into maintaining it, but that there's seemingly been very little (if any) interest in letting others maintain it despite several people expressing interest. I'm sure it's scare handing over commit access, but if you're giving it up anyway then why not just do it, see what happens? Instead it's just dead in the water.

I'd happily pay license fees to use Radix and/or Stitches, if that guarantees maintenance. Sadly that's not an option it seems.

I work on a lot of more "creative" projects where frameworks like TailwindCSS or Bootstrap just don't cut it. My approach has always been to use some kind of library to ease the process of creating my own CSS framework that can then be used by other people. I find that Stitches does it pretty well. You set your design tokens, then you have IntelliSense to help people understand the design system.

Some libraries, such as Stitches, claim near-zero runtime performance overhead by tackling the first issue (parsing JavaScript CSS objects). Nevertheless, they still inject the parsed CSS into the DOM at runtime, which means they haven’t entirely eliminated the performance concerns.

Stitches allows you to map your design system

Define strict system of colors, spaces, etc then attempt to synchronize usage of it in both design and code (tools like https://vanilla-extract.style/ or https://stitches.dev/ can help with enforcing system on software side)

Curious to understand what is trending. We've been big fans of Stitches, however, unfortunately the project is no longer maintained.

There are some issues with SSR and NextJS in React 18: https://github.com/stitchesjs/stitches/issues/863

According to the docs, NextUI is a React UI library that allows you to make beautiful, modern, and fast websites/applications regardless of your design experience. It is created with React and Stitches, based on React Aria, and inspired by Vuesax.

Stitches CSS customization