-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[RFC] CSS Modules → JSS #207
Conversation
Looks good to me. I'm still using the default styling, but having an easier way to override it seems like a win. One thing I wonder about is if the jss-isolate will affect the actual styleguided components base/global styles (things like |
Good point, I’ll check it. |
Something to think about: https://github.com/theme-standard/spec |
I don't know much about JSS in particular, but I remember being excited about the CSS-in-JS approach, then asking on SO if this was actually a good idea, and finally realizing that CSS as such actually makes a lot of sense. Around that time I also read a great followup on this discussion from @keithjgrant. So, proceed with caution :) |
@mik01aj I don’t believe in separation of CSS and JS ;-) but I still prefer CSS for its syntax and especially for available tooling. But here is not a regular site and even not a regular web app. Wee need our styles to be isolated from user styles: user styles (especially global styles like typography) shouldn’t affect style guide UI and vice versa. So I think JSS if a good solution for Styleguidist. It makes style overriding simpler and it’s not that hard to write it (and we don’t have a lot of styles anyway). |
# Conflicts: # loaders/styleguide.loader.js # src/index.js # src/rsg-components/ComponentsList/ComponentsListRenderer.js # yarn.lock
Merged to |
Why:
Styles overriding:
What do you think?