Hello,

Does anybody know if it's possible to apply a css class to a module? I didn't see anything in the settings... I know you can do color, border and alignment... but, it seems like it would make sense to be able to specify a css class that would be added to the module's outermost div.

Thanks,

Mike

ahh - cool - thanks Sebastian.

Maybe I will submit this to gemini though... it seems like it would make sense to get rid of some of those visual settings in the module and just replace them with an optional css class applied to the module... or at least to supplement them with an optional css class.

Thanks,

Mike

Hello,

I actually think it would make sense to have class options that can be set for both the page and the module. I probably wouldn't make a box to just type in page-specific CSS... but that might just be me.

DNN already has a framework for centralized portal css that can be customized separate from the skin. So, if administrators had tab and module classes they could apply, I don't see a reason why they couldn't put their actual css in the portal's css file. I think if tab-specific css was allowed, then that will encourage messy design standards. Since admins could accomplish the same outcome with their central css file, I wouldn't see an advantage to that setup, personally. 

I see a few specific use cases and advantages of tab/module classes and not tab-specific css:

1. Placing some modules that were designed for a desktop environment in a mobile skin can be problematic - this is particularly true for micro-site approaches to mobile where the mobile site is a subset of pages in the main portal. Here, module-specific css classes would let admins mark a module's class as "mobileLinks" or something and then centrally define how those should look different than their normal links module.
2. There is no downside/cost to un-used classes. So, if I do place a class on a module and then use it for one thing, but later want to get rid of it, I can just remove that from the portal.css file and I'm all set. It isn't going to hurt anything to have the additional class specified.
3. Using classes rather than actual css reduces redundancies - if you want two tabs to have a similar look, then just give them the same class. Otherwise, you'll have to copy/paste your css every time you want to make a change.
4. Using tab-specific css makes re-skinning more difficult. Say I have a few pages where I want some special css, but then later change skins... Now, I would have to go through each of those pages and change the settings. If I had centralized it, then I could just delete those entries in my portal CSS file and I'd be all set.

To me, I think the argument for adding module/tab class options is pretty solid.

Hope all's well,

Mike