DotNetNuke® Websites: Problem — Design — Solution

3.1. Problem

From its early days as IBuy Spy Portal, there has been a misconception that a DNN website has to have a certain look and feel. This was due in large part to the fact that developers were concentrating on writing source code without paying much attention to design, which was totally logical. As a result, early DNN skins had a "cookie-cutter" look and feel. After all, the initial focus of what is now called DNN was on function, not on design.

In the past year, things have changed quite a bit. As the DNN framework has become solidified and vilified, and now that more and more people have discovered it, the issue of design has become increasingly important, just like any other website. As a result, many so-called skinners — designers that create and offer DNN skins commercially — have come out of the woodwork. However, very few skinners take an out-of-the-box approach to creating DNN skins and so offer cookie-cutter designs that are similar in look and feel. This is typically what happens when designs are created simply to work on top of the DNN framework instead of creating a good design, and then tweaking it to work for DNN. The main point here is that the primary goal of the site should always be considered first: to provide a professional, intuitive, and highly functional graphical interface for users to interact with. Remember one simple fact: Appearance is important! Appearance is important! Appearance is important! You get the idea. The look and feel is the first ...