-
Notifications
You must be signed in to change notification settings - Fork 842
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSS modules roadmap #1335
Comments
@jasonrhodes I'm on board with this completely. I did some work two weeks ago as an experiment but got blocked by some of the engineery bits. Might make sense to do a quick zoom meeting to go over some ideas. What I generally want out of the system is...
Goals we're trying to solve.
|
Also goes without saying that once in EUI, we'd love to bring this to Kibana for many of the same reasons. Right now there is a lot of cascade crazyness down there where people are overwriting EUI base styling. |
I'll also be very interested in helping out here. Not at all tied to a given technical implementation (re: css-modules, etc.), but I've been hearing about this lately and wanted to at least give the concept a look: https://github.com/4Catalyzer/astroturf |
I'd be interested in helping here as well. |
Closing this in favor of #1656 which is the main tracking issue. |
I'd love to help take some of the lead on plotting a course for how this would work, based on what we did at my previous job with React, a design component library, and scoped CSS modules. To get that conversation started, can we use this issue to map out the general requirements for what "CSS" needs to do in EUI? To start:
Is that the gist?
The text was updated successfully, but these errors were encountered: