I've fixed my alignment issue, but it took some time to find it.

The StyleSheetWidget looks in it's baseURL path and adopts any css style sheets defined there.  One of these stylesheets was floating the widget to the right and even if I defined a float: left style in my skin.css the styles in the baseURL took precedance.

I've spent the last few weeks getting to grips with DNN and I think it's a great tool but it is definately let down by a lack of documentation.  Perhaps this is what you get when you pay for the other editions rather than just using the community edition?

I've been referring to the wrox publication "Professional DotNetNuke 5 Open Source Web Application Framework for ASP.NET" but I feel it skims over the skinning, menu skin objects and client widgets.  It also refers to the Extropy skin and asks you to install it, even though I've recently learned this skin is not available and for some reason wasn't released.

To summarise, my DNN experience is so far rewarding but also frustrating!

I agree compeltely. It wouldn't be so bad if their search box actually worked on this site. I've paid for the professional edition, gone through all the available documentation, and there's still nothing abotu widgets. I filed a support ticket with DNN support, and they helpfully pointed me to this thread. Which basically indicates to me that their support really isn't all its cracked up to be. The suggestion to read this thread came with a note that I might be interested in developer's support package (available in 10 developer-hour increments). It's pretty sad that I need to pay for developer support to learn how to use built-in functionality.

The support offerings for professional subscribers has been useful, but the entire experience is far less than I'd expected, and I feel downright sorry for anyone trying to make use of the Community Edition. Hopefully Microsoft will take notice and either support an alternative portal effort (so DNN will have some competition), or give these guys some money so that we (the community) can actually help improve the .NET ecosystem.