Re:Twitter Bootstrap without all the debt
by jqueryin on Friday November 15, 2013 @04:13PM
(#6742178)
I'm in the same camp. I know everyone is gung-ho on separation of the presentation layer, but I believe styles are far too intertwined into the presentation for semantic markup to be beneficial at a large scale. My primary concerns with semantic markup is that there's no quick way in your developer tools / inspector to lookup correlated rules in your LESS/SASS files and have them make sense (i.e. how many columns is this and how does it handle responsively?). As @bguthrie said, there's little you can deduce regarding relationships between the CSS file and the HTML markup. For this reason I stick with classes, as it's far easier to tell how my layout/grid is structured by simply viewing the source. I'm sure many will opinionatedly differ, but it's worked just fine for me for a decade and I find it easier to maintain and for other's to understand the structure on first glance of the HTML.
[ Parent
| on HN ]
Re:Twitter Bootstrap without all the debt
by scarecrowbob on Friday November 15, 2013 @04:22PM
(#6742235)
I recently started using source maps, which basically allow you to inspect the underlying less (I dunno about sass...). That might not totally fix your issues with inspecting correlated rules, or maybe you've already tried it, but I've been finding it helpful.
Sass can generate source maps too. :)
Re:Twitter Bootstrap without all the debt
by AlwaysBCoding on Saturday November 16, 2013 @01:22AM
(#6743907)
You should check out - http://brackets.io/index.html
It does a really good job at showing the relationship between HTML + CSS