I have a facility that I offer across multiple portals using global templates. I have just upgraded one portal to use a responsive skin, and had to change my template to use some skin specific CSS - e.g. div class="span3".

Now if that template is used on a portal where the skin/css does NOT contain class span3, there will be no effect - or rather the divs will assume default behaviour and this is just about OK. However, a greater problem is when a portal uses a different skin that might use a class of (say) colspan3 instead of span3

The only way I can see around this is to copy the global template and use different version per portal - but that is a logistical nightmare if I have to make changes.

I know I could use jquery to dynamically add the classes, but that would also prevent me using global templates - ie invoking the js would have to be in the template and so would need to be different per portal again

I am unaware of any technique I can use to alias the class names - e.g. my global template could specify div class="genericspan3", then somehow on a per-portal basis I make genericspan3 simply inherit (in the examples above) span3 or colspan3 as appropriate. 

Does anyone have a cunning solution to this?

TIA

Steve

Edited to add: Having just done a lateral think on this, I guess the answer is to indeed create and reference my own genericspan3 class in the portal css, and simply make it have the same attributes as the span3 or colspan3 class as appropriate for the portal concerned. I guess it's a change that only has to be made once - or at worst, once per portal skin change?