d for how scripts and programs are dynamically updated and how access to documents can be achieved (Dobson 23). These underpinnings of the development of dynamic Web pages underscore some of the industry issues, but do not reflect the impetus from which these Web pages came into focus. In order to understand the foundations for their development and their current significance, it is necessary to consider the progression from static Web pages to dynamic Web pages and then evaluate both the program elements and the implementation in order to gain a complete picture of the primary components of this industry directive.The Progression from Static Web PagesLess than a decade ago, when interest in the World Wide Web began to develop, Web sites were primarily static, and individuals had access through a direct choice of that site in order to view the information the site contained. Some developers recall the days when individuals would spend hours on what has been described as a “mental treasure hunt” searching for the best Web sites and then trading the information with others (Tebbe N23). Web sites, though active, were rarely interactive, and without an external “linked” capacity, they failed to provide support for further searches and limited the movement on the Web. The impetus for changing the static Web site came as a result of pressure to pay for site management, the pursuit of a justification for advertising costs that are Web-based, and the desire to build some profits into the nature of Web interactions, elements that could not inherently stem from the once-passive pages (Tebbe N23). The need for Web pages that could “reach out and touch us” was a fundamental component of the changing face of the World Wide Web, and developers have recognized the benefits of the more aggressive Web-based elements that have redefined the way that businesses, developers and individuals perceive the Web (Tebbe N2...
