One of the great advantages of using CSS is to separate content and presentation. Remember back in the day when we were all using spacer GIFs and font tags in our HTML? Oops, I think some of you out there are still using it in DotNetNuke development. Well, if you do, I strongly recommend that you should leave it behind. It is such an unpleasant experience when looking at the code especially when working in a team environment.
Today, using inline CSS is just like embedding font tags in your HTML. It is not a good practice in web development. Here are a few reasons why you shouldn't use inline CSS in your code (or in your skinning and UI design approach)
I’ve been there. So have hundreds of others. The nonsense styling of the default.css by developers, the non-standards approach that they take time to put in from regular text (.Normal), HTML headings (H1, H2, H3…in uppercase) to outdated CSS rules with the lack of knowledge in writing CSS shorthand to reduce file size and increase productivity. It’s all ended today.
For those of you who are experienced web developers that have adopted the web standards to reach out to the world, there is no need to struggle with using Firebug or IE Developer Toolbar to hunt for CSS attributes that should be overridden against the DNN’s default. I offer to you, the simplest solution—the default.css MUST DIE.
Each year, DotNetNuke Corporation gathers engineers, developers, designers, and many others whose work involve in Microsoft ASP.NET platform in one of the biggest events called OpenForce™. The purpose is to share knowledge and experience among professionals as well as networking opportunities with experts worldwide.
A few months ago DotNetNuke Corporation called for speakers to present at the annual North American conference in Vegas, I submitted my proposal with multiple topics surrounding DotNetNuke UI design, Skinning, and Web Standards.