All Articles

Articles

DotNetNuke, Skins

Standardizing on Telerik's RAD Menu

One of the biggest drains on our time has been the menu system. As a result, for the last year and on into the future, we now only build our skins using Telerik's Rad Menu. To be continued...

DotNetNuke, Skins

Efficion's Clean Skin

Image: Efficion's Clean Skin So many skins, so much bloat...

There are many thousands of skins out there in the DNN universe. Many companies specialize in producing skins for DNN and other CMS systems. I haven't spent a lot of time looking, but most of what I've seen, just isn't what I'm looking for.

As a developer with very strong HTML and CSS skins, and solid but limited image manipulation skills, what I really need is a good starting point so that I can quickly build out a custom skin that speaks to the personality of my client organizations.

Over the years, I've spent quite a bit of time producing and refining a skin that has exactly what I need to get started, and nothing extra. I have focused on creating truly clean, proper, HTML  that works on all (within reason) browsers. And the few nice clean images it does use make it easy to manipulate the skin into any color in the known universe.

You can see an image of this skin now. Soon, I'll be sharing the source of it with everyone. Many people simply won't get it, "Not enough pop", "where's the stock photos", "too generic", and that's fine, but I'd love to see the skin that ships with DNN be a lot more like this.

 

Read More...
Skins

CSS columns break down when things get complex

I'm so tired of people discounting HTML Tables. I'm a huge fan of CSS, I'm fully aware that it is possible to do columns using CSS, but in order to do so, you have to use a variety of hacks, and those hacks change based on a variety of circumstances.

With DNN, because we have skinning, we already have the needed separation between content and presentation. Tables are the best way to handle columns. They are rendered consistently across browsers, are clean, and easy to read and use, and provide capabilities that are very hard to get without Javascript hacks in CSS.

I've spent countless hours trying to work around problems with my CSS based columns due to one need or another. I've researched many approaches to the best way of handling them. None of the solutions I've seen have proven to be nearly as clean and easy as just using tables.

If you continue to feel compelled to build tableless designs, go for it, perhaps you'll have better luck than I, but when you have a complex need and you can't find a solution that works consistently in all browsers, I give you permission to just go ahead and use a Table.