Re: web site programming (not really).

> As much as I do like fancy web sites, If I could make a
> small web site out of one of my portals, with no errors.

First question: why, exactly, do you care about the errors?

> The hope is that it would be viewable reguardless of what browser, or  
> operating system the person uses to view the web site.

With the error-recovery in modern browsers, it's very hard to make a page  
that isn't viewable. Being viewable in a browser and conforming to [X]HTML  
/ CSS specifications are different things. You can have perfectly  
standards-compliant pages that won't render properly in MSIE, for example.

> we are trying to find a solution, that would work better
> then trying to guess as to what program is the best to use.

If you have a program that produces 100% valid HTML but won't let you use  
create any forms, does that mean the program is "better" than one that  
does let you make forms, but generates mark-up with a couple of errors?  
What if a program creates valid pages, but the pages look completely  
different when seen in different browsers?

The "best" program depends on each person's preference, and what they're  
trying to do. If there was a single "ultimate" solution, everybody would  
be using that. For some types of sites, you don't need an HTML authoring  
tool at all, you can just use a basic CMS. As long as the CMS templates  
are standards-compliant, your site should be, too.

You will find that most sites with a consistent cross-browser design and  
tidy, standards-compliant code were created with plain text editors (and  
the page code is usually generated by server scripts, it's not hard-coded  
HTML). The problem with WYSIWYG editors is that there's more to HTML than  
WYS.

RMN
~~~

Received on Monday, 5 May 2008 18:46:04 UTC