And another is bandwidth. My shop's policy is to work on a development
server, uploading changes only after fully deployed locally. Thus, while a
search-and-replace through 500 pages would indeed work from a maintenance
perspective, it becomes a hassle when all 500 need to be uploaded to the
site.

Even Dreamweaver's system requires this type of upload, which is why we
stopped using it as a site management tool back in 2003. Nowadays, we use
PHP includes.  Changing a site-wide menu requires editing of only a single
file.  Uploaded, this header file instantly propagates the change to all
pages that use it.

Combined with linked stylesheets, carrying changes throughout entire sites
is trivial compared to the way we did it a few years back.  I'm not going to
complain...:).

D

----- Original Message ----- 
From: "David Jones" <dvjones(at)ksbe.edu>

One drawback to having separate pages for each image
is that each page eats extra disk space.

• Web Designer Courses
• Off the Shelf Training Courses

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA