-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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
Distribute CSS files in releases #173
Comments
I completely agree. I tried "solving" this by doing: Which is very messy, and also, there's WAY too many overrides and dependencies. As this project is right now, it's only suitable for starting from scratch, as it is too dependent on deploying as is, and start expanding from the forked repo. |
AFAIK the project was intended for react-based applications: there are other frameworks implementing only the CSS. I guess the framework is meant to work with our own styles, so a compiled .css file doesn't make sense. Sure the docs should be more explicit about this (and provide better examples). I understand users having problems implementing it: not everybody uses less, gulp, es6 nor browserify. @TrySpace the docs app may help to understand how to build the less files. |
I think it would be useful to offer compiled js and css files. However, since these components depend on react, developers will at least need to understand how to use react components. It would also be really nice if we can customize this build and developers can just pick and choose which components get included in the compiled files. Also relates to #56 |
This may not be necessary if we do #30 . |
CSS / LESS files are no longer needed as of v0.8 |
material-ui would be much more user-friendly if it were possible to download it as a set of CSS files and examples. Currently there is a high barrier to using the project unless you're familiar with node/npm/browserify/react.
relates to #58 #63 #78
The text was updated successfully, but these errors were encountered: