<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Aaron Gerdes: Is your building up to code?</title>
    <link>http://www.aarongerdes.com/articles/2006/03/26/is-your-building-up-to-code</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Strategy, design, and technology to stand out and win business.</description>
    <item>
      <title>Is your building up to code?</title>
      <description>&lt;p&gt;In the &lt;a href="http://scobleizer.wordpress.com/2006/03/04/the-role-of-anti-marketing-design/"&gt;article quoted before on anti-marketing design&lt;/a&gt;, Scoble has tangent:&lt;/p&gt;


	&lt;blockquote&gt;
		&lt;p&gt;It&amp;#8217;s amazing how few corporate types get that the quality and engineering thought behind your &lt;span class="caps"&gt;HTML&lt;/span&gt; matters more than whether your site is pretty or not.&lt;/p&gt;
	&lt;/blockquote&gt;


	&lt;p&gt;Another way to put it: if your building is beautiful but not up to code, you&amp;#8217;re going to have problems.&lt;/p&gt;


	&lt;p&gt;Three reasons &lt;span class="caps"&gt;XHTML&lt;/span&gt;/CSS (business translation: recent) standards-compliant code is good for your business:&lt;/p&gt;


&lt;ol&gt;
  &lt;li&gt;&lt;strong&gt;Ease maintenance/updating/redesign costs.&lt;/strong&gt; Good code will separate the design/layout code from the formatted content. Doing so means that if you&amp;#8217;d like to change part of a page layout, you edit one &lt;span class="caps"&gt;CSS&lt;/span&gt; file instead of ten or hundreds of &lt;span class="caps"&gt;HTML&lt;/span&gt; files.&lt;/li&gt;

  &lt;li&gt;&lt;strong&gt;Lower costs for deploying content in other forms.&lt;/strong&gt; Related to the above. Create multiple stylesheets for a single body of content is easy. Now your website works on mobile phones and prints cleanly (yes, people still do that). Some will disagree, but I think standards-compliant code deploys better across multiple browsers and platforms. And it degrades gracefully (meaning old browsers will still see a readable version).&lt;/li&gt;

  &lt;li&gt;&lt;strong&gt;Accessibility: Better search engine ranking, wider audience.&lt;/strong&gt; Standards-compliant code is more organized and clean, therefore easily parsed for computers and people. This means screen readers and other assistive devices can process the information on your site for the sight-impaired, for example. It also (I&amp;#8217;ve heard this but cannot verify, so take with salt) can improve your search engine ranking by removing clutter and increasing your keywords-to-file-weight ratio.&lt;/li&gt;
&lt;/ol&gt;

	&lt;p&gt;Find out more about &lt;a href="http://www.webstandards.org/"&gt;web standards&lt;/a&gt;.&lt;/p&gt;</description>
      <pubDate>Sun, 26 Mar 2006 00:31:00 -0800</pubDate>
      <guid isPermaLink="false">urn:uuid:50558e9b-aff7-40fe-a4b2-1cb459157eef</guid>
      <author>aarongerdes@gmail.com (Aaron Gerdes)</author>
      <link>http://www.aarongerdes.com/articles/2006/03/26/is-your-building-up-to-code</link>
      <category>standards</category>
      <category>code</category>
      <category>validate</category>
      <category>web</category>
      <category>business</category>
      <trackback:ping>http://www.aarongerdes.com/articles/trackback/42</trackback:ping>
    </item>
  </channel>
</rss>
