3 ms·
I enjoyed the markup. Reminds me of the old days with font tags: <p class="pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l
by jaggederest 10y ago
I enjoyed the markup. Reminds me of the old days with font tags:
<p class="pageWrap pageWrap--s marginBottom-m paddingBottom-s c-slate lineHeight-l fontSize-l fontWeight-3 breakPointM-fontSize-xl breakPointM-lineHeight-xl">...</p>
and of course
<strong class="c-slate lineHeight-l fontSize-l fontWeight-5 breakPointM-fontSize-xl breakPointM-lineHeight-xl">9–14px</strong>
Seems a bit excessive, perhaps we could use a document to store all these classes in an organized fashion and then just refer to them by some sort of tagging system. We could link to that document from multiple pages, even, and change it without changing the base markup at all.
- polutropos 10y agoMarvel wrote detailed style guide/explanation and explained their use of the OOCSS style. https://marvelapp.com/styleguide/overview/code-guidelines https://marvelapp.com/styleguide/overview/code-guidelines
- jaggederest 10y agoOh I understand the style, I just think it's backwards. The whole point of CSS is to move the styling out of the markup, and this obviously fails atrociously in that regard. Each class is one CSS property, where it would be literally less verbose to just inline them. It's exactly the same thing as doing style="prop: value; prop: value;" since to change a given area of text from grey to black you'd have to edit every single element the same way.
- zepolen 10y agoThis looks like an April fools joke that someone took seriously.
- notahacker 10y agoThe irony is somewhere hidden in that forest of classes, I believe what they've actually done for most of the text for many viewports is to scale it down to "75%" or "18px"...