4 ms·
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
by jqueryin 13y ago
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.
- AlwaysBCoding 13y agoYou should check out - http://brackets.io/index.html http://brackets.io/index.html It does a really good job at showing the relationship between HTML + CSS
- Jacqued 13y agoDoes it now support multiple cursors (like CTRL+D on Sublime Text 2) ? Last time i checked, it didn't, and that is a deal breaker for me
- scarecrowbob 13y agoI 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.
- projct 13y agoSass can generate source maps too. :)