material-design-lite VS suit

https://getmdl.io/ No specific framework (e.g React, Angular) required

Also, since I was not sure if this was an MDL specific bug, I opted to post this question here instead of on their issues page. If anyone thinks I should post it there as well, let me know, and I can do that.

Material Design Lite - 32K⭐ - Last update: June 2017

Materialize, Material UI, Material Design Lite

I would recommend looking into an alternative such as https://getmdl.io/

Latest stable version: 1.3.0 Github stars: 31.8K Development: without activity for 5 years Long of active development: 2 years Active maintainers: 0 Contributors: 178 Number of commits: 2872 License: Apache Used by: 11.1K Github projects Git repository: https://github.com/google/material-design-lite

Projects: google/material-design-lite, tastejs/todomvc, GoogleChrome/workbox, GoogleChromeLabs/quicklink

google/material-design-lite - Material Design Lite Components in HTML/CSS/JS

As style sheets became the responsibility of larger and larger teams, CSS’ global scope and specificity were often at odds with team dynamics. Style collisions became increasingly common, where changes introduced by one developer would inadvertently affect styles elsewhere on the website. As the old joke goes: two CSS properties walk into a bar; a bar stool in a completely different bar falls over. As these issues and the number of people experiencing them multiplied, so too did new CSS methodologies, particularly those focused on style sheet architectures. Before long, we had SMACSS, SUIT CSS, BEM, ITCSS, and more. Third party supersets of CSS also appeared during this time, such as Sass and LESS, which gave style sheet authors access to scripting features like variables and loops.

CSS (Cascading Style Sheets) are rules to describe how your HTML elements look. Writing good CSS is hard. It usually takes many years of experience and frustration of shooting yourself in the foot before one is able to write maintainable and scalable CSS. CSS, having a global namespace, is fundamentally designed for web documents, and not really for web apps that favor a components architecture. Hence, experienced front end developers have designed methodologies to guide people on how to write organized CSS for complex projects, such as using SMACSS, BEM, SUIT CSS, etc.

This is actually super bad practice. I really dislike scoped css.

When I see devs using scoped css the class names always end up like `.box` or `.name`.

Having to think about classnames and writing Sass makes me much more aware of the structure of the components I'm styling. Frankly I think only JS oriented devs like scoped CSS and frontend who love html/css and the challenges of architecturing good CSS don't egt any benefit out of styled components (since you're using atomic css like Tailwind and/or BEM-style which always "scopes" classnames with the component name.

In general any solid guidelines makes CSS instantly 10x better and that's all most projects needs, and it's often what most projects lack.

SuitCSS works great with Vue in my experience, and can even be linted with postcss-bem-linter :

https://github.com/suitcss/suit/blob/master/doc/naming-conve...

SUITCSS

Tachyons developer, Adam Morse in this talk at DevShop London 2016, talks about motivation behind Tachyons. He discusses the problem of continuous over-riding your own written CSS code, writing tons of CSS code, struggle to keep all this info in your head and the need to refactor 200Kb CSS file. His answer to the problem is Tachyons. SUIT CSS (Style Tools for UI Components). was the initial inspiration that lead to creation of Tachyons. Unlike Bootstrap where you redefine a component multiple times, SUIT had a class which would not redefine itself or mutate later.

This component syntax is mainly taken from Suit CSS with minor modifications.

suitcss/suit - Style tools for UI components