Just thought I'd toss in my 4 cents on this one and offer a slightly different
perspective...
 
At our (manufacturing) site, we're using the Web to reduce the number of
HP3000 printouts that we have to distribute.  For instance, we put in a new
"back end" printing solution, use the Web instead of printing a hard-copy.  A
person carries out action x, and a short while later, the printout is HTML'd and
transmited over to our main Web server where it is WAIS'd and made
available in TABLE format, along with 2 weeks prior history for action x.
 
Action x used to be done by one clerk, who had a printer in her area.  Given
what we've done, she does very few action x's now (and she's happy about
that!!!)  That work load is spread out over the several engineers who gave the
actions to her and are closer to the product anyway.  As importantly, webbing
the printout, makes it available to anyone who needs it (security allowing).
From the shipping people, who can do a WAIS search for a particular
product/item/container/etc, to the folks who plan our production, to the folks
who function as quality control.
 
 
<<Sidebar:  Anyone notice the need to *move the "printout" from* our HP3000
to our main web server for WAISing.  Meaning the lack of WAIS on the 3000...
HP?  Anyone?>>
 
 
I believe that most of the discussion on this thread has centered around Web
sites for "outsiders" to look at (aka "dog-and-pony" shows) and decide on
products to purchase, for information about company, or just to show off cool
stuff.  To tell the truth, that's probably what most people use it for; but, for us, at
least, there are other users to be considered.
 
Since our stuff is internal and we're not "selling" something some of our
general design philosophy goes like this:
 
1) use graphics to make your point, but use them sparingly.  Also use ALT
whenever possible.
 
2) if you use graphics for "spiffyness", make sure that they won't impede those
who CAN'T or CHOOSE not to load your graphics.
 
3) graphics (image maps) shouldn't control anything.  If you can't view it, you
can't control it.
 
4) try to use only the most standard html.  when you can't do that, make sure
that those who will be viewing your html will have capable browsers or are
forewarned.
 
5) try to make any particular page no more than 3 jumps away.  That makes
sure that the users have an easy time navigating, and don't need a page and
a half full of bookmarks to remember where to go.
 
Our pages aren't designed for flashyness, they're designed for regular use by
people who use it as a tool.  We want them to be pleased with their
environment, but we also we recognize that they're there for a reason and
don't want to waste their time with things they don't need.
 
Phew!!!  That was more than a mouthful, and I deleted more than you've read.
My point being, that there are many, many possible uses for the Web, internal
and external.  Some of the design considerations are different for different
uses; some are the same.  It's dependent on the point of your page(s).  Are
you on the "bleeding edge" and you want to show other "bleeding edgers"
your coolest stuff?  Are you utilitarian, and want nothing more than functionality?
 Or, like most, are you somewhere in between?  As with any paper document,
your design should be, at least partially, dictated by those who will read your
page(s).
 
 
My 6 cents worth,
 
Randy Smith
Hoechst Celanese - Shelby Plant
[log in to unmask]
<speaking for myself, not anyone else>