View Full Version : Why Use XHTML?


Arizona Web
06-11-2004, 08:34 PM
[SIZE=4]Why Use XHTML on Your Web Site?[/SIZE] by Chris Hooley of MCP Media, Inc.

As web site owners, we all want the same thing. We all want a great design. We all want to make money. We all want our site to reach as many people as possible. But how often have you heard "My site looks great at home but I looked at it on this different computer and it looked like crap!"?

Chances are you've heard this before, or maybe you've even said it yourself. Thankfully, good web developers know how to avoid this, and still deliver everything you should expect from a good web site.

Many web design companies only understand certain portions of creating a great web presence. Some companies focus on web development, but have limited design and marketing skills. Others are so focused on bleeding edge technology and design that they forget that some people view websites on PDAs or alternative browsers that can't support such technical wizardry. Few firms can find that sweet spot in the middle where your web site looks great and functions well in all instances. Enter XHTML and cross browser compatibility.

What is XHTML?
XHTML is the W3C standard for developing cross browser compatible web sites. It fuses all of the display elements of HTML with some of the functionality of XML. By forcing a web designer to program more carefully and adhere to strict code standards, XHTML allows a larger percentage of browsers or code parsers to properly parse your documents. In less geeky terms, it means more people can see your site the way you meant for them to see it, and less people see your site with elements strewn all over their page.

For your site to reach the widest potential audience, it is important that it is developed in the most cross browser compatible method possible. XHTML is that method. The rise of handheld internet ready devices is forcing lazy web designers to program their sites more efficiently, since most internet ready cell phones and PDAs require XHTML to be able to view web sites properly. People who use mac computers often see a bunch of gibberish on their screen when browsing the web because some of the tools web design "professionals" use create bloated code that does not render properly. Lazy programmers often only use WYSIWIG (what you see is what you get) editors to create their web pages and don't even bother to open up the code window.

When somebody comes to your site and sees a total mess of graphics and tables all over the place, it is your brand and your site that suffers. No company looks good with a site that looks bad. Let's do a short exercise to prove this point.

Right now think of me as a user who is ready to buy a widget. You sell widgets. I just landed on your home page. Your site looks awesome on my computer at home running Internet Explorer. However, today I am browsing around on my neat new cell phone. Chances are if you're site is not XHTML compliant; it looks terrible to me right now. I don't want to see this mess on my new toy, so to clean my screen, I just click right past you and into your competitor's home page. Unfortunately for you, their site is programmed in XHTML and looks perfect.



That's it, I'm sold... and I just bought this shiny new widget from your competitor.


--------------------------------------------------------------------------

Chris Hooley (http://www.mcpmedia.com/corporate_info/chris-hooley.php) is a web design and web development specialist and founder of MCP Media, Inc. MCP Media (http://www.mcpmedia.com) is a Phoenix Arizona based web design, web development, and internet business development firm.

owlcroft
06-11-2004, 11:00 PM
That is well put, and all quite true. Moreover, XHTML is the wave of the future: in times not so far off, you really won't have a web site if it isn't coded in XHMTL.

Right now, XHTML Transitional 1.0 is easily achieved by a little global replacement, a modest amount of time spent with a third-party validator, and more care in future. Down the road, XHTML 2.0 (http://www.xml.com/pub/a/2003/03/19/dive-into-xml.html) will be a very tough nut to crack for those not already positioned at XHTML 1.0.

Currently, most browsers except Mozilla do not handle validated xhtml (or html) very well: IE is notoriously unfaithful to the w3c standards. But that is bound to change with time--not even very-small-and-limp can stay behind the times forever.

RideQ
06-16-2004, 06:31 PM
Hey, Im sold on it!
:D

seo guy
06-18-2004, 04:10 PM
Great Post AZ Web, would you like it posted on the site as web design article? If so PM me or email me a BIO and picture and I'll create a non xhtml compliant bio page for you just like I did for Eric :-) http://www.seo-guy.com/authors/eric-walker.html Nothing to salesy please just who you are and what you do etc
Cheers

xml
06-20-2004, 06:06 AM
You might wanna note how XHTML can vastly reduce the size of webpages, when used with CSS. Check our xmltraining.com in my sig, note the tiny file size.

Your right about XHTML 2.0 owlcroft, its a major overhall e.g. like IMG tags will be replaced with OBJECT tags.

wyrickj
06-22-2004, 01:21 PM
Why oh Why does Microsoft not follow the W3C Standards? I mean every one wants them to as I saw on there Channel9 forum on MSDN that there was this thread on what people wanted on the next version of IE and most said that they wanted IE to follow the standards. Also why does Microsoft donate money to them when they don't follow the standards?

xml
06-23-2004, 01:11 AM
They do follow standards, just to a different degree to some other organisations.

wyrickj
06-23-2004, 10:11 AM
Well they don't fully support XHTML and I wish they did and they do not fully support CSS2 ether. I mean I love IE and I do not even want to use Mozilla or Netscape but a friend uses Firefox and said my site looks kinda messed up as I design for IE. I hope IE 6.05 fully supports W3C Standards. BTW IE is no longer going to be avalible in a Standalone version. Updates and Patches will be avalible but if you want to get IE 6.05 or 7 when it comes out you would need to buy Windows Longhorn (Currently a few years down the road from the final release.) I may write an article on the New Web Services while I am thinking of it.