<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Why Standards Still&#160;Matter</title>
	<atom:link href="http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/feed/" rel="self" type="application/rss+xml" />
	<link>http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/</link>
	<description>Design.  Art.  Writing.  Markup.  Life.</description>
	<pubDate>Thu, 22 May 2008 20:19:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: me</title>
		<link>http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-274</link>
		<dc:creator>me</dc:creator>
		<pubDate>Thu, 21 Sep 2006 18:14:53 +0000</pubDate>
		<guid isPermaLink="false">http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-274</guid>
		<description>Joe,

There's no reason to be a jerk.</description>
		<content:encoded><![CDATA[<p>Joe,</p>
<p>There&#8217;s no reason to be a jerk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jina Bolton</title>
		<link>http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-273</link>
		<dc:creator>Jina Bolton</dc:creator>
		<pubDate>Thu, 21 Sep 2006 17:56:18 +0000</pubDate>
		<guid isPermaLink="false">http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-273</guid>
		<description>[quote comment="272"]If standards matter to you so much, why does your site use inline styles?[/quote]

I'm not done with this site, &#38; it's possible that there are some inline styles scattered around from the K2 theme or from plugins.  I'll eventually get to all of these.</description>
		<content:encoded><![CDATA[<blockquote cite="http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-272"><p>
If standards matter to you so much, why does your site use inline styles?</p>
</blockquote>
<p>I&#8217;m not done with this site, &amp; it&#8217;s possible that there are some inline styles scattered around from the K2 theme or from plugins.  I&#8217;ll eventually get to all of these.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joe</title>
		<link>http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-272</link>
		<dc:creator>joe</dc:creator>
		<pubDate>Thu, 21 Sep 2006 16:26:33 +0000</pubDate>
		<guid isPermaLink="false">http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-272</guid>
		<description>If standards matter to you so much, why does your site use inline styles?</description>
		<content:encoded><![CDATA[<p>If standards matter to you so much, why does your site use inline styles?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jina Bolton</title>
		<link>http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-269</link>
		<dc:creator>Jina Bolton</dc:creator>
		<pubDate>Wed, 20 Sep 2006 22:19:58 +0000</pubDate>
		<guid isPermaLink="false">http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-269</guid>
		<description>[quote comment="268"]For what it's worth, I agree with Nate. You do have a groovy cool site.[/quote]

Thanks, Bryan!

I still have lots on the to-do list to finish it.  :)</description>
		<content:encoded><![CDATA[<blockquote cite="http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-268"><p>
For what it&#8217;s worth, I agree with Nate. You do have a groovy cool site.</p>
</blockquote>
<p>Thanks, Bryan!</p>
<p>I still have lots on the to-do list to finish it.  :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan S</title>
		<link>http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-268</link>
		<dc:creator>Bryan S</dc:creator>
		<pubDate>Wed, 20 Sep 2006 21:46:21 +0000</pubDate>
		<guid isPermaLink="false">http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-268</guid>
		<description>For what it's worth, I agree with Nate. You do have a groovy cool site.

And I think you both are doing a great job of explaining the benefits of using web standards. There probably isn't much more you can do except continue to be patient. Sucks, doesn't it?

One note about the search engines... Most only look through a certain amount of code on each page. So if you simplify your code, they will be able to read more of the content. I think most also try to match meta keywords with headings (h1-h6 tags) and content. But headings usually carry a heavier weight, so if you use semantic h1-h6 tags instead of paragraph tags with fonts or some other old school technique, the search engines will love you even more. And face it, isn't it really about the love?

Who would've thought it would be so tough to get professional web designers/developers to use semantic code (aka: use HTML tags the way they were meant to be used in the first place)?</description>
		<content:encoded><![CDATA[<p>For what it&#8217;s worth, I agree with Nate. You do have a groovy cool site.</p>
<p>And I think you both are doing a great job of explaining the benefits of using web standards. There probably isn&#8217;t much more you can do except continue to be patient. Sucks, doesn&#8217;t it?</p>
<p>One note about the search engines&#8230; Most only look through a certain amount of code on each page. So if you simplify your code, they will be able to read more of the content. I think most also try to match meta keywords with headings (h1-h6 tags) and content. But headings usually carry a heavier weight, so if you use semantic h1-h6 tags instead of paragraph tags with fonts or some other old school technique, the search engines will love you even more. And face it, isn&#8217;t it really about the love?</p>
<p>Who would&#8217;ve thought it would be so tough to get professional web designers/developers to use semantic code (aka: use HTML tags the way they were meant to be used in the first place)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jina Bolton</title>
		<link>http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-267</link>
		<dc:creator>Jina Bolton</dc:creator>
		<pubDate>Wed, 20 Sep 2006 14:52:38 +0000</pubDate>
		<guid isPermaLink="false">http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-267</guid>
		<description>It's a tough battle sometimes.  Usually when I start spouting off my "beliefs" with standards, I get a deer-in-the-headlights expression, so I have learned to tone it down.

With clients, I talk about how CSS/(X)HTML sites are easier to manage, which saves time (which save money).  I talk about search engine rankings (because from what I can tell, sites created by standards &lt;em&gt;do&lt;/em&gt; tend to rank better.)  For a while there, accessibility seemed to only be a concern to government-related clients, but lately I seem to be getting more &#38; more questions about 508-compliancy (which makes me happy).  What seems to also gain the client's attention to standards is the discussion on mobile technologies (because all of them seem to carry Treos these days...)

With other designers/developers, it's actually trickier.  Most of the "non-believers" seem to consider the browser-consistancy war to be a waste of time &#38; energy.  Sometimes I can win them over by talking about updates being easier &#38; showing them &lt;a href="http://csszengarden.com/" rel="nofollow"&gt;CSS Zen Garden&lt;/a&gt;, but I am finding I am still struggling with this.  One thing I've noticed, however, is that they do perk up when they notice the site load faster, or that a change takes me less than a minute (while it would have taken them ten or more...).  I use these moments to remind them of the beauty of CSS.  :)

It's not easy.  I still find myself battling the Microsoft-Kool-Aid-drinking-Internet-Explorer-only people.  I've tried showing them lawsuits &#38; horror stories, but that hasn't been as effective as I would have liked.  Like you said, showing by example &lt;em&gt;really&lt;/em&gt; is the best way.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a tough battle sometimes.  Usually when I start spouting off my &#8220;beliefs&#8221; with standards, I get a deer-in-the-headlights expression, so I have learned to tone it down.</p>
<p>With clients, I talk about how CSS/(X)HTML sites are easier to manage, which saves time (which save money).  I talk about search engine rankings (because from what I can tell, sites created by standards <em>do</em> tend to rank better.)  For a while there, accessibility seemed to only be a concern to government-related clients, but lately I seem to be getting more &amp; more questions about 508-compliancy (which makes me happy).  What seems to also gain the client&#8217;s attention to standards is the discussion on mobile technologies (because all of them seem to carry Treos these days&#8230;)</p>
<p>With other designers/developers, it&#8217;s actually trickier.  Most of the &#8220;non-believers&#8221; seem to consider the browser-consistancy war to be a waste of time &amp; energy.  Sometimes I can win them over by talking about updates being easier &amp; showing them <a href="http://csszengarden.com/" rel="nofollow">CSS Zen Garden</a>, but I am finding I am still struggling with this.  One thing I&#8217;ve noticed, however, is that they do perk up when they notice the site load faster, or that a change takes me less than a minute (while it would have taken them ten or more&#8230;).  I use these moments to remind them of the beauty of CSS.  :)</p>
<p>It&#8217;s not easy.  I still find myself battling the Microsoft-Kool-Aid-drinking-Internet-Explorer-only people.  I&#8217;ve tried showing them lawsuits &amp; horror stories, but that hasn&#8217;t been as effective as I would have liked.  Like you said, showing by example <em>really</em> is the best way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate K</title>
		<link>http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-266</link>
		<dc:creator>Nate K</dc:creator>
		<pubDate>Wed, 20 Sep 2006 14:21:55 +0000</pubDate>
		<guid isPermaLink="false">http://jinabolton.com/writing/archives/2006/09/20/why-standards-still-matter/#comment-266</guid>
		<description>I think it was a great article. I commented there, but i love your site too so I am going to comment here :)

What do you think is the best approach to handling those who arent in tune with standards? I have found that being abrasive doesn't really help - but how else do you get the message across?

Personally, I have found that by DOING things by example helps the most. I  have worked with some local developers lately. Sitting down with them, working with them, showing them simple things - this seems to help the process the most. The fact that they can see their old example, and my new example redone in CSS - and how much it shaves from load times and filesizes. The fact that they can see a semantic approach to their content and structure. Just starter discussions, but its progress nonetheless. 

I learn from books and from colleagues. I read alot. I get involved alot - but I wasn't always that way. I used to be the person I get annoyed with today. Having friends like Stephen who - though  he has more knowledge than me, never spoke down to me but simply showed me by example. Those things meant more to me than someone preaching standards to me. 

So, what do you think the balance is?</description>
		<content:encoded><![CDATA[<p>I think it was a great article. I commented there, but i love your site too so I am going to comment here :)</p>
<p>What do you think is the best approach to handling those who arent in tune with standards? I have found that being abrasive doesn&#8217;t really help - but how else do you get the message across?</p>
<p>Personally, I have found that by DOING things by example helps the most. I  have worked with some local developers lately. Sitting down with them, working with them, showing them simple things - this seems to help the process the most. The fact that they can see their old example, and my new example redone in CSS - and how much it shaves from load times and filesizes. The fact that they can see a semantic approach to their content and structure. Just starter discussions, but its progress nonetheless. </p>
<p>I learn from books and from colleagues. I read alot. I get involved alot - but I wasn&#8217;t always that way. I used to be the person I get annoyed with today. Having friends like Stephen who - though  he has more knowledge than me, never spoke down to me but simply showed me by example. Those things meant more to me than someone preaching standards to me. </p>
<p>So, what do you think the balance is?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
