On 10/21/16 11:52 AM, Angela French wrote:
Passing along a recent article worth reading: https://seesparkbox.com/foundry/thoughtful_css_architecture
This is good, on the whole, though it misses what constitute (IMO) the most important approach to simplification: markup patterns.
(First corollary: a good stylist has a finger on the pulse of both markup and CSS. Second corollary: the ever-popular approach of putting front-end engineers - too many of whom are refugees from older disciplines in which the conventional wisdom remains that HTML and CSS are toys - in a different silo entirely is perhaps the single most important reason why I'm ordered to take beta blockers twice a day.)
In practice, yes, you're going to use classes to tell objects/components apart, and if you're doing a good job of simplifying your markup, then you'll need to distinguish e.g. a list intended for case {x} from one intended for case {y}. With that established, do try to avoid relying on namespace-y things to accomplish what you can manage with a vanilla DOM. Comments in working files impose negligible overhead, classes-all-over-the-place not so much.
Everything that follows from this turns into a further litany about project mismanagement; a lot of stylesheets-gone-topsy that I see are overgrown because of ill-advised platform choices, just-get-it-done management style, and/or a high-level refusal to acknowledge Brooks' Law.
...Done now. I'm gonna go into the kitchen and studiously ignore what's happening on my lawn.
-- Ben Henick lurker...@henick.net Sitebuilder At-Large t:@bhenick ______________________________________________________________________ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
