<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Keep CSS clean</title>
	<atom:link href="http://www.fuzzylizard.com/archives/2009/04/14/1038/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fuzzylizard.com/archives/2009/04/14/1038/</link>
	<description>Web development and design with a little VFX thrown in for fun</description>
	<lastBuildDate>Fri, 14 Jan 2011 22:45:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Bernd Eckenfels</title>
		<link>http://www.fuzzylizard.com/archives/2009/04/14/1038/comment-page-1/#comment-34402</link>
		<dc:creator>Bernd Eckenfels</dc:creator>
		<pubDate>Thu, 16 Apr 2009 05:00:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/?p=1038#comment-34402</guid>
		<description>Yes agreed. Consistent elements across multiple plages is a good thing, and CSS is the first place you can see if you violate that.</description>
		<content:encoded><![CDATA[<p>Yes agreed. Consistent elements across multiple plages is a good thing, and CSS is the first place you can see if you violate that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Johnston</title>
		<link>http://www.fuzzylizard.com/archives/2009/04/14/1038/comment-page-1/#comment-34401</link>
		<dc:creator>Chris Johnston</dc:creator>
		<pubDate>Thu, 16 Apr 2009 00:49:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/?p=1038#comment-34401</guid>
		<description>I definitely agree with reserving the use of h1-h6 tags solely for describing elements of content.

As for using different renderings based on content, I would have to say that the more consistent you can have things across your site, the better things are going to look. The more I can style an h3 tag once and keep it the same, the easier it is for my users to recognize what they are looking at. This applies to all the different elements on the page.

There may be exceptions to this rule, but I would suggest thinking real hard before you add custom renderings for something and ask yourself why need it.

The more consistent your site is, the easier it is for your users to, well, use.</description>
		<content:encoded><![CDATA[<p>I definitely agree with reserving the use of h1-h6 tags solely for describing elements of content.</p>
<p>As for using different renderings based on content, I would have to say that the more consistent you can have things across your site, the better things are going to look. The more I can style an h3 tag once and keep it the same, the easier it is for my users to recognize what they are looking at. This applies to all the different elements on the page.</p>
<p>There may be exceptions to this rule, but I would suggest thinking real hard before you add custom renderings for something and ask yourself why need it.</p>
<p>The more consistent your site is, the easier it is for your users to, well, use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bernd Eckenfels</title>
		<link>http://www.fuzzylizard.com/archives/2009/04/14/1038/comment-page-1/#comment-34398</link>
		<dc:creator>Bernd Eckenfels</dc:creator>
		<pubDate>Wed, 15 Apr 2009 04:10:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/?p=1038#comment-34398</guid>
		<description>I somewhat disagree. If you do semantic markup with heading levels you do have to use different renderings based on the context.

However it might also be wrong to use headings for things like navigation. Reserve the h1-h6 for the body/content.

Greetings
Bernd</description>
		<content:encoded><![CDATA[<p>I somewhat disagree. If you do semantic markup with heading levels you do have to use different renderings based on the context.</p>
<p>However it might also be wrong to use headings for things like navigation. Reserve the h1-h6 for the body/content.</p>
<p>Greetings<br />
Bernd</p>
]]></content:encoded>
	</item>
</channel>
</rss>

