4 ms·
Not sure I get it. It sounds like it is a css file which styles standard html elements. But I'm not sure. If so, where is the css file? And what are those 200
by TekMol 2y ago
Not sure I get it.
It sounds like it is a css file which styles standard html elements.
But I'm not sure. If so, where is the css file? And what are those 200 files in the git repo?
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- croes 2y agoThere is a link to the CSS under Usage. https://matcha.mizu.sh/#usage https://matcha.mizu.sh/#usage https://matcha.mizu.sh/matcha.css https://matcha.mizu.sh/matcha.css
- 0cf8612b2e1e 2y agoThese classless libraries are for quick/MVP style web apps where you just need to give the user one or two forms and some help documentation. I use them all the time for internal stuff because it lets me write some dirty html and have the backend do the real work while not looking browser-default-hideous. If you need something more complicated, these are probably not meant for you.
- easyThrowaway 2y agoYep. I love the idea behind those libraries but I can't think of any production environment where I would use them without crippling any future change. You'd be forced to silo every custom component from the main stylesheet.
- lowlighter 2y agoYeah I don't think this is meant to be used for a production environment. I wrotten this mostly to style my hobby projects effortlessly Anyway more "professional contexts" probably have their own branding too, so the added value is probably negligeable in this case
- lowlighter 2y agoYes it's exactly as you guessed it The hundreds of files in the repo are just for maintainability and organization, but in the end it'll result in a single file to include, although you can also individually select which part you want to include if you'd like