Re: [w3c/webcomponents] Change 'CSS Modules' name to avoid webdev confusion (#843)

There are 2 problems here, IMO:

## Term for SEO is needed

Speaking about "CSS with zero tools", as opposed to "CSS produced by tools" (preprocessors / plugins), people usually name it "vanilla CSS" and that's can be easily recognised.

So I would recommend to use the following name in blogs, articles etc for SEO:

> Vanilla CSS modules 

And of course, specification should name the thing what it actually is: "CSS modules".

## Library positioning adjustment

I strongly recommend to rename [CSS modules](https://github.com/css-modules/css-modules) to something like "CSS hashes". Also, its positioning should be adjusted so at least this (very questionable) statement

> No global scope.

Would be realistically re-phrased as follows:

> Global scope with generated CSS class names.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/843#issuecomment-536893043