Many times I have been asked the same question by various clients regarding the DotNetNuke CSS load order. Many of them were having difficulties when customizing their modules and skins to have uniform styles. Simply understanding the DotNetNuke CSS hierarchy is essential when performing these tasks.
Understanding DotNetNuke CSS precedence:
- Assists you to create detail-oriented and professional DotNetNuke skins
- Helps to troubleshoot issues with CSS in various context after installing skins and applying to use in a production environment (especially cross-browser troubleshooting)
- Provides the advantage to design your website in a consistent manner by customizing the modules in DotNetNuke
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)