You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just wanted to make it more explicit that it is in the Readme:
This org's purpose is to collect discussion about all the possible requirements of a component-oriented CSS solution for JavaScript. There are a lot of libraries out there already, many of which solve most of these problems, but all the discussions around them are fractured across twitter, medium, issues and gists.
So we're trying to approach it from a different perspective: collect the ideas and discuss the issues in a single place, making it easier for the community to follow and engage with.
Hopefully, one (or more) of the current crop of libraries evolves to a point where they meet the goals & requirements we work out through this collaborative process. If not, maybe we have a spec to build one. If any of the existing libraries have either (a) technical limitations preventing them from being the whole solution, or (b) different design goals, that's cool - that is no judgement on them, and it's very unlikely a "one size fits all" solution is possible.
If you lead, or know of, a library that works well for css components, shout out here and consider adding an implementation to the comparison repo!
The text was updated successfully, but these errors were encountered:
BTW, since you mentioned react-select, it might also be worth setting up some strawman for what you want the API for theming library components to look like. I think that could focus discussion fairly nicely.
I just wanted to make it more explicit that it is in the Readme:
This org's purpose is to collect discussion about all the possible requirements of a component-oriented CSS solution for JavaScript. There are a lot of libraries out there already, many of which solve most of these problems, but all the discussions around them are fractured across twitter, medium, issues and gists.
So we're trying to approach it from a different perspective: collect the ideas and discuss the issues in a single place, making it easier for the community to follow and engage with.
Hopefully, one (or more) of the current crop of libraries evolves to a point where they meet the goals & requirements we work out through this collaborative process. If not, maybe we have a spec to build one. If any of the existing libraries have either (a) technical limitations preventing them from being the whole solution, or (b) different design goals, that's cool - that is no judgement on them, and it's very unlikely a "one size fits all" solution is possible.
If you lead, or know of, a library that works well for css components, shout out here and consider adding an implementation to the comparison repo!
The text was updated successfully, but these errors were encountered: