<?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: Top 5 Best CSS Organizational Tips</title>
	<atom:link href="http://infectthesystem.com/2009/top-5-best-css-organizational-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://infectthesystem.com/2009/top-5-best-css-organizational-tips/</link>
	<description>Your source for everything web</description>
	<lastBuildDate>Sun, 11 Apr 2010 13:24:21 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adam Gardiner</title>
		<link>http://infectthesystem.com/2009/top-5-best-css-organizational-tips/comment-page-1/#comment-1117</link>
		<dc:creator>Adam Gardiner</dc:creator>
		<pubDate>Sat, 16 May 2009 05:35:41 +0000</pubDate>
		<guid isPermaLink="false">http://infectthesystem.com/?p=132#comment-1117</guid>
		<description>@ganarce - Thanks for the comment! I got the idea of the general elements, and specific elements, but what exactly would be contained inside the special elements section?</description>
		<content:encoded><![CDATA[<p>@ganarce &#8211; Thanks for the comment! I got the idea of the general elements, and specific elements, but what exactly would be contained inside the special elements section?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Gardiner</title>
		<link>http://infectthesystem.com/2009/top-5-best-css-organizational-tips/comment-page-1/#comment-1116</link>
		<dc:creator>Adam Gardiner</dc:creator>
		<pubDate>Sat, 16 May 2009 05:33:30 +0000</pubDate>
		<guid isPermaLink="false">http://infectthesystem.com/?p=132#comment-1116</guid>
		<description>@Tom - Nice CSS work! The only thing I think you could improve on that (visually anyway) would be to make the comments stand out a little bit more for the different sections. 

But other than that, yea I would be proud of that CSS file too! Good job.</description>
		<content:encoded><![CDATA[<p>@Tom &#8211; Nice CSS work! The only thing I think you could improve on that (visually anyway) would be to make the comments stand out a little bit more for the different sections. </p>
<p>But other than that, yea I would be proud of that CSS file too! Good job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ganarce</title>
		<link>http://infectthesystem.com/2009/top-5-best-css-organizational-tips/comment-page-1/#comment-1113</link>
		<dc:creator>ganarce</dc:creator>
		<pubDate>Thu, 14 May 2009 14:12:24 +0000</pubDate>
		<guid isPermaLink="false">http://infectthesystem.com/?p=132#comment-1113</guid>
		<description>Good article:

I&#039;m using blueprint as a starting point and then I have a file with my custom modifications divided in 3 sections:


Special elements position, size , structure
General elements design
Specific elements design (menus, login widgets and others)
</description>
		<content:encoded><![CDATA[<p>Good article:</p>
<p>I&#8217;m using blueprint as a starting point and then I have a file with my custom modifications divided in 3 sections:</p>
<p>Special elements position, size , structure<br />
General elements design<br />
Specific elements design (menus, login widgets and others)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Freeman</title>
		<link>http://infectthesystem.com/2009/top-5-best-css-organizational-tips/comment-page-1/#comment-1112</link>
		<dc:creator>Tom Freeman</dc:creator>
		<pubDate>Thu, 14 May 2009 13:57:57 +0000</pubDate>
		<guid isPermaLink="false">http://infectthesystem.com/?p=132#comment-1112</guid>
		<description>Some good advice there thanks. I&#039;ve thought for a while how there weren&#039;t really any clear guidelines on good organisational layout for CSS code. Over the years, like you, I&#039;ve developed a way that makes sense to me (along similar lines as you&#039;ve described actually). Except I now tend to put everything on the one line (per style anyway) check my css to see what I mean (I&#039;m quite proud of it lol)
http://www.webchalkboard.com/css/screen.css</description>
		<content:encoded><![CDATA[<p>Some good advice there thanks. I&#8217;ve thought for a while how there weren&#8217;t really any clear guidelines on good organisational layout for CSS code. Over the years, like you, I&#8217;ve developed a way that makes sense to me (along similar lines as you&#8217;ve described actually). Except I now tend to put everything on the one line (per style anyway) check my css to see what I mean (I&#8217;m quite proud of it lol)<br />
<a href="http://www.webchalkboard.com/css/screen.css" rel="nofollow">http://www.webchalkboard.com/css/screen.css</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
