Comments on: Web Standards Aren’t Necessary and Hurt Your Website http://www.mediamarketers.com/blog/index.php/2007/09/15/web-standards-arent-necessary-and-hurt-your-website/ Tips for Getting and Growing Online Thu, 22 Jul 2010 21:41:25 -0400 http://wordpress.org/?v=2.9.1 hourly 1 By: Ian Gordon http://www.mediamarketers.com/blog/index.php/2007/09/15/web-standards-arent-necessary-and-hurt-your-website/comment-page-1/#comment-4 Ian Gordon Sun, 30 Sep 2007 15:50:21 +0000 http://www2.mediamarketers.com/blog/index.php/2007/09/15/web-standards-arent-necessary-and-hurt-your-website/#comment-4 You raise some good points, however, we are talking about ROI I am assuming. If say, a client then wants a part of the site re-designed, with tables or other proprietary code, you have to start from scratch, the structure would have to be rebuilt everytime you code a site, since as you said yourself, the nesting and complication of using tables becomes a nightmare with re-designs and simple changes. The idea being using (X)HTML and CSS is that you have a standard, whereby, all different sorts of devices can accept the underlying data and using CSS you can format a new and proper design for each device, whereas with tables you would have to design completely different site for each device. Standards are simply a way to making something universal, rather than specific to one device or design. CSS and (X)HTML offer flexibility, which is rather nice. Yes, you spend a little more time working out some kinks but, if it can mean greater flexibility and ability to just up and change the design without touching the base (X)HTML and content, then I think it is worthwhile. Though, to each their own. You raise some good points, however, we are talking about ROI I am assuming. If say, a client then wants a part of the site re-designed, with tables or other proprietary code, you have to start from scratch, the structure would have to be rebuilt everytime you code a site, since as you said yourself, the nesting and complication of using tables becomes a nightmare with re-designs and simple changes.

The idea being using (X)HTML and CSS is that you have a standard, whereby, all different sorts of devices can accept the underlying data and using CSS you can format a new and proper design for each device, whereas with tables you would have to design completely different site for each device.

Standards are simply a way to making something universal, rather than specific to one device or design. CSS and (X)HTML offer flexibility, which is rather nice.

Yes, you spend a little more time working out some kinks but, if it can mean greater flexibility and ability to just up and change the design without touching the base (X)HTML and content, then I think it is worthwhile. Though, to each their own.

]]>