@codesatori and @*

"Whatever we call it, you still need to define separate CSS classes for each module under each skin, rather than deriving similar or near-identical units from a generic CSS class for simply 'units' or 'posts'."

You should never have to "define separate CSS classes for each module under each skin" The only time you should ever have to do that is if you are making a custom design specific to the module outside of what the current boonex module CSS offers see more OR if you are creating your own modules. However with a properly created module, it will automatically take the design of the current template whatever that may be. That would be the correct method. All other times the template CSS and templates are inherited by the modules.

It sounds to me like everyone in this thread is working from the module > template. That is the wrong way. You have to go from template > module. The modules inherit from your template and not the other way around. If it were the first case then mastermindsro logic is correct and that would be insane and boonex will have to change their template approach. However, that is not the case.

@codesatori - as a programmer you must be familiar with an overloaded method. It's the same thing -- this time it's with the module's CSS, images and html.

If one of you can post a sample of your directory structure in the next hour I might be able to see why you are all touching the modules CSS when in fact you don't have to unless you are doing something unique or custom to that module. If I don't see a post then I will ignore this thread and you can all continue doing your templates that way you "think" it should be done.

This place needs a solid templates tutorial.