Adobe Dreamweaver and Contribute were used on the UM campus up through 2009. The Cascade Content Management system was introduced in the fall of 2008 and and many sites were in the CMS by the summer of 2009.
One of the major differences is seen in process of saving web pages and publishing them to web servers. In the Cascade model, all editing is done within the Cascade system. Pages are not "live" on a web server until the pages are published to the development server (staging.umt.edu) or the live server (usually www.umt.edu) or to both at the same time.
The Dreamweaver model provided direct editing on local pages (either stored on individual computers or on our since-retired Development server) with the ability to "put" those files to the live web server. Although the wyisiwyg nature of Dreamweaver allows a close preview of the page, it is common practice to view the page through a web browser to see the final product. That could happen as soon as a page was saved, either by viewing the local page on the desktop computer or on the development server or by "putting" the file and viewing it on the live web server.
Dreamweaver's model was that any editing was done on local web pages (either on the local computer or on the development server). Once perfected, those pages are then "put" to the live web server - www.umt.edu.
Less common on campus, the Contribute model allowed limited but direct editing on the live web server. Again, the page could be previewed within Contribute or by publishing to the live web server and viewing it there. This process bypassed a developmental server completely. Files were edited on the "live" web server, perhaps stored as a draft, and then, when ready, published "live" to www.umt.edu.
