And just to add to this further, where is the burden for ensuring a consistent look? Is this purely an admin task (associate the module with the skin) or something that is done when content is edited on the page.

For example, if I have a module that supports adding text entries of some type (like a blog, for example), with a header and some body text, how does the person creating the text specify the style for the header ? Does this simply boils down to selecting styles in a rich text editor?

I am asking about the general case - I assume that some of these questions are module specific in how they expose their functionality.

Thanks.

Mark

Hi Mark, as Sebastian said, it all depends on the module developers. However, what I would suggest is that you use Firebug to see the CSS associated with the classes, ID's and HTML tags that the module is using. Then, you can override or append additional CSS properties in your CSS file. e.g. suppose that you find that a div in the module that has the class="myDiv"with properties {color:red;} and you want the text in that div to be blue, then all you need to do is that in your CSS you put div.myDiv {color:blue;}. The way CSS is loaded in DotNetNuke is that the module's CSS is loaded before your portal's CSS. Thus, your CSS property will override the module's CSS property, in this case effectivelymaking the text blue. This is obviously a limited solution since if for example the module developer has used inline CSS (i.e. style="color:blue") in his HTML, then this will override your CSS. However, provided that an external stylesheet was used by the developer, what I am recommending can be a viable solution.