Totally - thanks Brad. (Although I have a follow-up question below :))
That is what I thought initially - only, it seemed like OOcss has the
'encapsulated' form as in OO-programming.
From looking at the UML diagram and reading expressions such as 'all
classes made available to [some class]', I was under the impression
that the hierarchy is enforced intrinsically.
Rather, it is the responsibility of the user to make it work by
grouping compatible css styles, which can be done by following the
OOCSS API - so it sounds like OOCSS offers modules (CSS libraries)
promoting a new standard of best practices?
Would this be an accurate description? I will dig into the exercises
to get a better grasp.
KC