Topic on Manual talk:Coding conventions/CSS

Note to whom it may apply to, including myself: https://perishablepress.com/obsessive-css-code-formatting-organization-comments-and-signatures/

We currently have a plethora of code comment styles, which could be exchanged by a guideline in order to make navigation large chunks of CSS/Less code easier.

From an IRC comment:

I just looked at comments on normalize.css https://github.com/necolas/normalize.css/blob/master/normalize.css and I like how they do this "annotation" style comments

@Quiddity (WMF) Was this from you or from another user? From my POV a solution here should be in alignment with other comment styles. I think, when we could come up with one clear hierarchy markup and align the most used files, rest will get aligned by itself. In contrast to majority of other parts in CSS our current (great!) grunt-stylelint solution doesn't cover comments. So we'd need to rely on manual activity.

From someone else, but I forget where or who. (I think they had logged-off, hence I didn't ask them to post it themselves, or if I could attribute it).

I also found this article (whilst searching for syntaxhighlight references), where the first section is entirely about code-comments, and its advice is the complete opposite of the comment I pasted above: https://medium.com/@MrJamesFisher/your-syntax-highlighter-is-wrong-6f83add748c9

I don't know enough about other code comment styles, to be able to give useful input myself.

Do we use minification of some sort, for the CSS that is sent to the browser? That might be relevant, when deciding between large comment blocks vs inline-micro-comments.

@Quiddity (WMF) Code comment length is not an issue, comments are not sent over the wire in majority of cases.