For all I know there could already be a module that does this but it would be fantastic if under advanced settings there was the ability to tell a text/html or any other module to use a specific class or id without digging into skin files.

For example if I wanted a text/html module to float right I'd just update the skin.css and then under advanced properties type in the name of the id or class.

The attached image shows what I mean a bit better.

Use the Header and Footer of the advanced module settings to wrap a div tag around the module, and specify the css class to be used.

That's what I've been doing so far however that adds extra divs which isn't the most semantic way to do things. By adding the ability to specify a specific css class or id for a module you can clean up and speed up the site as well speed up development time.

I agree. Why don't you make that suggestion at dotnetnuke.com.

Thanks for the suggestion jncraig. I've made the suggestion: http://support.dotnetnuke.com/issue...&PROJID=23

Great. The whole community gains when people make suggestions.

Each module does already have a unique ID assigned to it.

For instance, go to: http://www.dnncreative.com/tabid/75...fault.aspx

Using the web developers toolbar go to the Information menu / Display ID & Class Details

From here you can see the main Text / HTML module has a unique ID of #dnn_ctr380

There are various variations of this ID, you will be able to view:

#dnn_ctr380_contentpane .dnnC_content_transparent DNNAlignleft
#dnn_ctr380_ModuleContent
#dnn_ctr380_HtmlModule_lblContent .Normal

We can target the main content area of the Text / HTML module with:

#dnn_ctr380_contentpane
{
border: 10px solid orange;
}

For further info on the web Developers Toolbar view:Troubleshooting DotNetNuke Skins

I'm a huge fan of the web developers toolbar. The problem is those unique identifiers are too unique since the unique id's are assigned dynamically as you add modules to a page giving you much more extra work in the backend customizing your aspx files rather than letting you use a minimal amount of divs and styles.

If I wanted to style the top left text/html module on all of my pages without rewriting the module or adding extra divs I'd need something like:

#dnn_ctr408_ContentPane { background: #e3e3e3; float:left; width: 165px; }
#dnn_ctr409_ContentPane { background: #e3e3e3; float:left; width: 165px; }
#dnn_ctr410_ContentPane { background: #e3e3e3; float:left; width: 165px; }
#dnn_ctr411_ContentPane { background: #e3e3e3; float:left; width: 165px; }
#dnn_ctr412_ContentPane { background: #e3e3e3; float:left; width: 165px; }

and on and on depending on the number of pages I have in my site.

However if I can assign an id or class of my own choosing then I'd only need to add "#TopLefttextbox" and it would work on all of my pages.

The way the current method is there's no real intrinsic difference I can see between the old preCSS method of every element having font tags and background colors as part of the source rather than the current css method of abstracting layout completely from the source code.

Yes for multiple instances the unique ID method will not be suitable, but for one off styling it is very useful.

the method I currently use is to specify elements in special containers. - this way if you need a "float right" div adding to a text HTML module, you can do it by simply using that container on the module,  so you no longer have the problem of multiple entries of code.

But, it still won't be as simple as the idea you have mentioned,  it will be interesting to see if it is implemented, thanks,