I discovered something we should probably follow for class
names: the
WSRP 1.0 specification (PDF) in section 10.6 actually defines a collection of
CSS classes and says in part:
One of the goals of an aggregated page is a common look-and-feel across the Portlets contained on that page. This not only affects the decorations around the Portlets, but also their content. Using a common CSS style sheet for all Portlets, and defining a set of standard styles, provides this common look-and-feel without requiring the Portlets to generate Consumer specific markup. Portlets SHOULD use the CSS style definitions from this specification in order to participate in a uniform display of their content by various Consumers. For markup types that support CSS stylesheets, Consumers MUST supply a CSS stylesheet to the End-Users agent with definitions for the classes defined in section 10.6 of this specification.
Even if we don't end up implementing WSRP, they seem well thought out and ultimately a good starting point.
There are some proposals for WSRP 2.0 (due later this year) to add some further classes but I didn't track them down.
