Some of you may remember this thread on OOCSS from a while back: http://www.sitepoint.com/forums/css-53/object-oriented-css-uses-learning-newbie-740553-2.html
In it, there was a link to a video of Nicole Sullivan presenting her brain child to a YDN group: Stubbornella » Blog Archive » Object Oriented CSS video on YDN
There is also an article about it here: Meet Object Oriented Css Cut The Fat Out Of Code With This Smart Time Savin | Articles | Meta Q (which is rather short).
I wanted to watch it way back then, but stuff got in the way and I didn’t watch it until today.
Now, I’d like to revise my stance a bit.
For those of you that don’t know, the basic premise is that you use class which essentially represent different “objects”. Then, to style your HTML, instead of creating unique styles for each object that’s slightly different, you give it multiple classes to describe the element using your already made blocks.
I don’t think this solution is perfect, but I do thing it’s certainly worthwhile to learn about (or at least watch the video).
It is definitely not a perfect system, however, I can definitely see advantages to using it. I’m in the process of wrapping up a redesign of a site with roughly 1,200 pages. In this case, I see where this system could have saved us considerable time.
The system does call for avoiding IDs, which makes sense in most cases. However, the religious avoidance of IDs would also be kind of pointless for one-off cases which always crop up.
What are your opinions on OOCSS? Have you ever used it in a project?