Originally Posted by noonnope
oocss is a concept, it is not a framework. It is a way to take styling similar elements beyond page detection based on applying application level meaning expressed by classes to common visual concepts used to deliver content and/or functionality to the end user. Getting it right involves identification of those common concepts which can be difficult at times since they will not always be the same. However, when done correctly the concept itself eliminates redundant code and provides an accelerated means of making global style changes with high level of granular control.
The concept is really as simple as this:
No none semantic mark-up or anything just applying meaning considering the form element itself does not provide enough information to separate it from all the other "types" of forms that may be getting used on a site. That is really all it is or all I have ever seen it as. To go a step further and create a framework based on commonly used components isn't the core idea. That is essentially what bootstrap is – the main one that comes to mind.
When there is absolutely no semantic relationship between styling the elements similar practice what ralph.m suggested. Generally those types of styles will be placed in a CSS file establishing the overall look and feel. Where as, styles that affect specific cases/pages will go else where.
Originally Posted by haopei
Just noticed this thread is over 6 months old...