RFC: CSS in JS with fela

Motivation: this comment

We’ve considered CSS in JS for a long time. We have our hands tied right now when it comes to CSS. We cannot create new components (e.g. DateTime) as we cannot create new styles. We also cannot fix CSS issues when they arise.

CSS in JS also offers us a solution to far better theming capabilities than CSS preprocessors. If done well we could, in fact, compile down to CSS, LESS, and SCSS if users would like to still use those flavors.

I’ve been researching and prototyping around this issue for a couple years now. I’ve held off due to lack of stability and maturity in the CSS in JS community, which I’m mostly now satisfied with. I am also finally in a position where I need a CSS in JS framework for business purposes. I wish I could have used SUIR for this new task, however, due to the lack of CSS in JS, I cannot.

Help!

This leaves me with two choices, port SUIR to CSS in JS and use it or write a new framework using all the utils and patterns from SUIR.

Pinging @Semantic-Org/react-admins, @Semantic-Org/react-maintainers, and @Semantic-Org/react-collaborators. If I were to kick off a css-in-js branch, would this be something you would want to contribute to?

I know the community would love to have this as well.

[fracmak]

It’ll be very useful if you could document how the class names are changing to help build a migration guide to ease anyone like me who’ve written override styles occasionally when it’s needed.

[layershifter]

Closing this issue for housekeeping 🏠

See stardust for CSS in JS: https://github.com/stardust-ui/stardust