Web Standards: Why You Should Use Them

  • Thread starter Shannon
  • 4 comments
  • 449 views
Yeah, I've been coding my sites lately using XHTML 1.0 transitional, and CSS for design. However, I don't recommend that people use CSS-P yet (in other words, using CSS for positioning elements), because such designs deteriorate badly in older browsers, and even the current 5th gen browsers don't have the great support for such things (IE still refuses to use the fixed positioning CSS property, which really irks me, since it would be a very good frames substitute). Hopefully though, we'll be seeing better CSS 1/2 support in the near future. :)
 
Yeah, and all you have to do to convert your HTML page to an XHTML page is change the DOCTYPE code at the top to:
Code:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd ">

And then change the first HTML tag to:

Code:
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 
Well, for those whoa already have pages, there's quite a bit more to it than that. ;) I can say that, because I've personally done it... I switched from HTML 4.0 to XHTML 1.0 Transitional a couple months ago, and I'm still in the process of changing some of my older pages.

For one, with all of the tags that have been depracated, you not only have to change those tags, but make the proper work-arounds in CSS, and that's a grueling task, especially if your site was done by hand (with Dreamweaver, it's a bit easier, since it highlights incorrect syntaxes and you can make some changes via the Properties toolbar). However, I think it's well worth the effort, considering how it'll make it easier for designers to make a website look like what they want it to look like without dealing with quirks in the system. 👍
 
Hmm. Does Adobe ImageReady export to XHTML (after slicing up a page)?

I guess i'll start doing my pages in XHTML.. Shouldnt be too hard to convert, seeing as i write all my html in lowercase anyway. ;)
 
Back