I have never heard of HTML / CSS, and I'm not sure if you really need it.
The main theme of style guides is to quickly read code using familiar visual layouts and naming conventions, so that developers know that they are doing something, because that’s the way they would put it / name it. HTML / CSS offers far fewer options for changing the way it works than a complex language like JavaScript. HTML, which is markup and strictly nested, creates a specific layout, and CSS has only one code construct, so you are left with names that, since they do not describe actions and do not process data, rarely require very complex ones.
As for JavaScript, as in any language, you need to choose a set of standards and stick to them. It doesn't really matter which of them will always love the other. Consistency is key, so the only thing you need to look for is a collection that matches the multitude of any large libraries you work with. One project I'm working on has its own rules for PHP, which should also be used for JavaScript. This makes it weird when camelCase () is used in the library code, and other code uses the words _separated_by_underscores () for function names.
Another minor issue may be that your favorite IDE may or may not have good support to enforce a specific set of standards through its automatic formatting / error. One-click fixes for inaccurate code are sometimes a real luxury!
source share