|
|
4.1.4 "Why Do I Need a Dynamic Web Solution?" [The following is based on an article by Jonathan Wall entitled "Why Go Dynamic?" in the Macromedia Edge Newsletter.]
Let's look at the advantages of dynamic versus static development. Dynamic development allows you to:
Develop Fewer Pages Traditionally, sites are constructed with a large number of static HTML pages. By serving up pages and information dynamically, the number of pages can be dramatically reduced. Take the example of an employee directory. A static employee directory has one page that lists all the employees, and it provides a detail page with information about individual employees. Not only does the main directory need to be updated when a new employee is hired, but also must be created for that employee detail page. Furthermore, a web designer or developer must update the page. To create a dynamic employee directory, you would need an application server and a database that connects to your intranet. Keep Content Fresher By moving from static to dynamic, site content can be maintained more easily. Dynamic sites also help to ensure that the most accurate, timely information is available to those who need it. Continuing with the employee directory example, when you work with a static employee directory and a new person starts at your company, it may take a while for human resources to provide you with that employee's personal information. Once you get the information, you need to update the main directory listing (using HTML) and create a detail page that has all the employee's information. Then, you need to link the main directory to the new employee's detail page and FTP. While you are working, users of the directory may want to call the new employee but can't because they are waiting for you to update the directory and/or push the page live. The directory isn't as fresh as it could be, and people are frustrated because they have to wait for content. If you had a dynamic site, web page developers wouldn't even need to be involved. As soon as the new employee's information became available, the HR team could enter data into the directory via a browser-based admin module (no HTML required). This situation empowers the HR team to keep the directory current and frees the web developer to work on more challenging projects. Additionally, with a dynamic site, new information can be available immediately, with no need for waiting. Dynamic sites make it easy to keep content fresh. The employee directory is only one example, of how you can save time and precious development effort by going dynamic. Many other web-based services take advantage of dynamic applications, including weather reports, headline news, and online stock tickers. Future-Proofing the Site Change is constant in today's economy. Web sites perceived to be easily alterable need to change as well. Customers, both internal and external, now look to the web sites as the leading source of the most up-to-date information available. Imagine that your company puts the corporate headquarters address and phone number on the bottom of every page on the static site. Then your company moves. Your web site could have hundreds or thousands of static pages, if not more. If you included that information in static text on each page, imagine having to update each and every page. It would take days, if not weeks, to do this. Now look at the same problem for a dynamic site. If the pages are built dynamically, they can be based on templates, and all that would need to be updated is the portion of the template containing the company address and phone number. Instead of thousands of updates, one minor update would update the site instantly. Dynamic sites help you make your web site future-proof changes can be made without requiring additional maintenance by web developers in order to stay current. See Examples of Dynamic Web Projects Examples of Slicksurface's work with these types of projects can be found in the Dynamic Web section of the Slicksurface Showcase.
|
|