<?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: Guidelines for Developing Your Own CSS Framework</title>
	<atom:link href="http://www.w3avenue.com/2009/04/01/guidelines-for-developing-your-own-css-framework/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.w3avenue.com/2009/04/01/guidelines-for-developing-your-own-css-framework/</link>
	<description>Advice &#38; Resources For Rapid Web Development</description>
	<lastBuildDate>Mon, 08 Mar 2010 13:27:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tyler Diaz</title>
		<link>http://www.w3avenue.com/2009/04/01/guidelines-for-developing-your-own-css-framework/comment-page-1/#comment-182</link>
		<dc:creator>Tyler Diaz</dc:creator>
		<pubDate>Thu, 21 May 2009 13:46:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.w3avenue.com/?p=256#comment-182</guid>
		<description>You could also try using PHP to do the job for you so you can keep your CSS files organized - yet still keep the correct way of how it should be presented.

There&#039;s a pretty solid trick presented here: 
http://www.ethanandjamie.com/blog/43-web-dev-freebies/85-php-gzip-css-files</description>
		<content:encoded><![CDATA[<p>You could also try using PHP to do the job for you so you can keep your CSS files organized &#8211; yet still keep the correct way of how it should be presented.</p>
<p>There&#8217;s a pretty solid trick presented here:<br />
<a href="http://www.ethanandjamie.com/blog/43-web-dev-freebies/85-php-gzip-css-files" rel="nofollow">http://www.ethanandjamie.com/blog/43-web-dev-freebies/85-php-gzip-css-files</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eren Emre Kanal</title>
		<link>http://www.w3avenue.com/2009/04/01/guidelines-for-developing-your-own-css-framework/comment-page-1/#comment-19</link>
		<dc:creator>Eren Emre Kanal</dc:creator>
		<pubDate>Fri, 03 Apr 2009 03:34:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.w3avenue.com/?p=256#comment-19</guid>
		<description>Thanks.

Just one little note; you may want to combine all the css files in one file. That&#039;s because of performance issues. X different css files mean X http requests. So minimum is better.</description>
		<content:encoded><![CDATA[<p>Thanks.</p>
<p>Just one little note; you may want to combine all the css files in one file. That&#8217;s because of performance issues. X different css files mean X http requests. So minimum is better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Montoya</title>
		<link>http://www.w3avenue.com/2009/04/01/guidelines-for-developing-your-own-css-framework/comment-page-1/#comment-18</link>
		<dc:creator>Montoya</dc:creator>
		<pubDate>Fri, 03 Apr 2009 01:08:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.w3avenue.com/?p=256#comment-18</guid>
		<description>It&#039;s very good to see what&#039;s out there and try all the different options for CSS frameworks. Blueprint, for example, has been developed by a community of CSS experts and contains a lot of heavily tested &amp; sound ideas. At the very least, you should always start with a good reset that will eliminate the discrepancies across browsers so you can hit the ground running.</description>
		<content:encoded><![CDATA[<p>It&#8217;s very good to see what&#8217;s out there and try all the different options for CSS frameworks. Blueprint, for example, has been developed by a community of CSS experts and contains a lot of heavily tested &amp; sound ideas. At the very least, you should always start with a good reset that will eliminate the discrepancies across browsers so you can hit the ground running.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: korbinian polk</title>
		<link>http://www.w3avenue.com/2009/04/01/guidelines-for-developing-your-own-css-framework/comment-page-1/#comment-15</link>
		<dc:creator>korbinian polk</dc:creator>
		<pubDate>Thu, 02 Apr 2009 18:05:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.w3avenue.com/?p=256#comment-15</guid>
		<description>thanks for the inspiration! i&#039;m creating a css &#039;framework&#039; for me personally right now, so i can use all the input i can get.</description>
		<content:encoded><![CDATA[<p>thanks for the inspiration! i&#8217;m creating a css &#8216;framework&#8217; for me personally right now, so i can use all the input i can get.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FatGeek</title>
		<link>http://www.w3avenue.com/2009/04/01/guidelines-for-developing-your-own-css-framework/comment-page-1/#comment-14</link>
		<dc:creator>FatGeek</dc:creator>
		<pubDate>Thu, 02 Apr 2009 09:20:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.w3avenue.com/?p=256#comment-14</guid>
		<description>Dude, I knew this is how you do it. But thanks for providing the plan - some good tips(bookmarked it - wish me good luck). Great resources too...</description>
		<content:encoded><![CDATA[<p>Dude, I knew this is how you do it. But thanks for providing the plan &#8211; some good tips(bookmarked it &#8211; wish me good luck). Great resources too&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
