DotNetNuke® Websites: Problem — Design — Solution

6.1. Problem

When developing static websites, pages must be created and edited offline as independent HTML files and uploaded to the server to have changes/updates take effect on a live website. Typically, a qualified webmaster who has a working knowledge of HTML, CSS, and other web technologies does this. First, the webmaster has to be contacted and briefed about the required updates. Next, the webmaster must schedule time for the required updates. And finally, when the webmaster finds time in his/her schedule, the necessary required files have to be downloaded, edited, uploaded, and then tested. This creates a highly inefficient system for making even the simplest of updates to a website.

Static websites also don't provide flexibility, efficiency, or intuitiveness in terms of making changes to a website's hierarchy. Typically, several files have to be updated in order to make a simple change, such as moving a page within the site to another location within the same site. A system such as this is not an efficient way to update a website.

It isn't just static websites that lack flexibility, adeptness, or intuitiveness—many Content Management Systems have a less-than-straightforward approach when it comes to administering pages. Some do not even allow you to edit pages directly. In many cases, you have to navigate to a separate Admin area to apply updates, and then click a Preview button, which launches a separate window, just to see what you've done. One of the really cool things ...