Then I'd say, since there has to be a standard, let's use XHTML, which will
make sure we don't have a lot of retrofitting to do in a few years. The
historical example you can cite is Cascading Style Sheets. They require
closed paragraphs and closed list items, so that the styles don't get mucked
up. If you had begun using recommended HTML practices a few years ago, your
site is ready for CSS now without having to do a lot of fixing of old code.

By adhering to XHTML standards now, your pages will also be ready for
"alternative" browsing devices which may be developed in the future. The
favorite example we use on this list is the web-enabled refrigerator.

And since it's a team, take a vote on it.

---------------------------------------------------------
Chuck Evans
Web Marketing Manager
Captura Software, Inc.
(425) 424-1155
chucke(at)captura.com
http://www.captura.com

-----Original Message-----
From: Reywob(at)aol.com [mailto:Reywob(at)aol.com]
Sent: Monday, June 26, 2000 2:09 PM
To: hwg-techniques(at)hwg.org
Subject: Re: TAG case; XHTML; Flame Wars.

In a message dated 6/26/00 9:36:19 PM GMT Daylight Time, Chucke(at)captura.com 
writes:

> I don't see why you bother arguing with her. Let her code any way she
wants
>  to. If she doesn't want to write "well-formed" code, then that's her own
>  business.

It matters because the team is building a support site, with a lot of 
templates being used.  Therefore we all need to standardise the code to make

it easy for the other members to work with.

• Web Designer Courses
• Off the Shelf Training Courses

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