[thelist] Site check: Staples.com

Ken Schaefer Ken at adOpenStatic.com
Wed Sep 21 01:11:03 CDT 2005


> -----Original Message-----
> From: thelist-bounces at lists.evolt.org [mailto:thelist-
> bounces at lists.evolt.org] On Behalf Of Anthony Ettinger
> Sent: Wednesday, 21 September 2005 3:36 PM
> To: thelist at lists.evolt.org
> Subject: RE: [thelist] Site check: Staples.com
> 
> > > > Unless there's a payoff, there's no point
> > > > spending the money.
> > > >
> > >
> > > Oh...but there is a payoff, if you're a large
> > > site.
> > >
> > > Using divs and 1 css file will slim down your site
> > > considerably, saving you in bandwidth costs.
> >
> > This wasn't a tables -vs- divs argument. The
> > argument is whether the site is
> > "broken", and whether a site owner needs to support
> > every different user out
> > there with every different possible level of
> > functionality enabled. I'm
> > arguing that it's only worth doing this /if/ there
> > is a sufficient pay off in
> > doing so.
> >
> 
> Well, I'm just telling you what I've read. The
> business can be made for accessibility. I'm certainly
> not telling you that you have to recode your site. But
> if I were building from the ground up, it's something
> I would definitely consider.

Absolutely - to quote what I said in a previous post:

"in the design phase considerations about the type of functionality the end
user will need to have will be discussed and signed off on. This would
include an analysis of the types of users the site's already getting and the
type of functionality they have enabled. At this point the cost/benefit of
requiring certain functionality should be discussed and determined."

In the design phase you'd look at all these issues and determine what makes
the best business sense for the project in question. Whether there's a payoff
or not is something that really depends on the situation.

Cheers
Ken


More information about the thelist mailing list