<?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: 9 CSS Best Practices You Need to Know</title>
	<atom:link href="http://fwebde.com/css/css-best-practices/feed/" rel="self" type="application/rss+xml" />
	<link>http://fwebde.com/css/css-best-practices/</link>
	<description>Helping people to make fantastic websites, whether you are a designer, a developer, or someone just who loves websites.</description>
	<lastBuildDate>Fri, 23 Jul 2010 12:14:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: PHP Best Practices For Beginners - Fantastic Web Design</title>
		<link>http://fwebde.com/css/css-best-practices/comment-page-1/#comment-1489</link>
		<dc:creator>PHP Best Practices For Beginners - Fantastic Web Design</dc:creator>
		<pubDate>Mon, 12 Apr 2010 14:12:41 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=1221#comment-1489</guid>
		<description>[...] CSS Best Practices [...]</description>
		<content:encoded><![CDATA[<p>[...] CSS Best Practices [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SM</title>
		<link>http://fwebde.com/css/css-best-practices/comment-page-1/#comment-1182</link>
		<dc:creator>SM</dc:creator>
		<pubDate>Tue, 09 Feb 2010 07:35:51 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=1221#comment-1182</guid>
		<description>Excellent tips. Thanks</description>
		<content:encoded><![CDATA[<p>Excellent tips. Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Orr</title>
		<link>http://fwebde.com/css/css-best-practices/comment-page-1/#comment-1170</link>
		<dc:creator>Stephen Orr</dc:creator>
		<pubDate>Mon, 08 Feb 2010 07:15:03 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=1221#comment-1170</guid>
		<description>For me, the best reason to put each rule on it&#039;s own line is simple - version control! Some merge tools find it hard to work with text changes on a single line, so you&#039;d have more potential for issues keeping the rules together.</description>
		<content:encoded><![CDATA[<p>For me, the best reason to put each rule on it's own line is simple - version control! Some merge tools find it hard to work with text changes on a single line, so you'd have more potential for issues keeping the rules together.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: twe4ked</title>
		<link>http://fwebde.com/css/css-best-practices/comment-page-1/#comment-1158</link>
		<dc:creator>twe4ked</dc:creator>
		<pubDate>Sun, 07 Feb 2010 06:52:09 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=1221#comment-1158</guid>
		<description>I agree, this one is personal choice!</description>
		<content:encoded><![CDATA[<p>I agree, this one is personal choice!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Semblance</title>
		<link>http://fwebde.com/css/css-best-practices/comment-page-1/#comment-1143</link>
		<dc:creator>Semblance</dc:creator>
		<pubDate>Fri, 05 Feb 2010 19:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=1221#comment-1143</guid>
		<description>I agree with Alex, I personally prefer my selectors to be in one line. Less scrolling through all the lines to make changes or add something. I use to do it the way you prefer. I guess it is up to personal preference. In one line it can sometimes be hard to read.
I have actually never thought to have a colour reference in the top of the CSS file. I still go back and forth to Photoshop. Will definitely use that tip from now on. Thanks.</description>
		<content:encoded><![CDATA[<p>I agree with Alex, I personally prefer my selectors to be in one line. Less scrolling through all the lines to make changes or add something. I use to do it the way you prefer. I guess it is up to personal preference. In one line it can sometimes be hard to read.<br />
I have actually never thought to have a colour reference in the top of the CSS file. I still go back and forth to Photoshop. Will definitely use that tip from now on. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Bannatyne</title>
		<link>http://fwebde.com/css/css-best-practices/comment-page-1/#comment-1138</link>
		<dc:creator>Eric Bannatyne</dc:creator>
		<pubDate>Fri, 05 Feb 2010 15:28:14 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=1221#comment-1138</guid>
		<description>That&#039;s actually a very good point. When I was writing this article, I just picked the first example that came to my head. I&#039;ll update the post with a better example.

Thanks for reminding me!</description>
		<content:encoded><![CDATA[<p>That's actually a very good point. When I was writing this article, I just picked the first example that came to my head. I'll update the post with a better example.</p>
<p>Thanks for reminding me!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Orr</title>
		<link>http://fwebde.com/css/css-best-practices/comment-page-1/#comment-1135</link>
		<dc:creator>Stephen Orr</dc:creator>
		<pubDate>Fri, 05 Feb 2010 11:12:40 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=1221#comment-1135</guid>
		<description>Avoid using inline styles? I agree with the sentiment - you ABSOLUTELY should avoid inline styles - but what you&#039;ve replaced it with is almost as bad.

You&#039;ve created a class called .redbox - but this a totally non-semantic name, and doesn&#039;t give any indication of what it represents. What happens if you decide that every red box should now be blue?

Do you change the .redbox class to have a blue background, do you create a new .bluebox class and do search/replace throughout all your HTML?

Or do you just call .redbox something like .infobox that represents it&#039;s purpose rather than it&#039;s colour.</description>
		<content:encoded><![CDATA[<p>Avoid using inline styles? I agree with the sentiment - you ABSOLUTELY should avoid inline styles - but what you've replaced it with is almost as bad.</p>
<p>You've created a class called .redbox - but this a totally non-semantic name, and doesn't give any indication of what it represents. What happens if you decide that every red box should now be blue?</p>
<p>Do you change the .redbox class to have a blue background, do you create a new .bluebox class and do search/replace throughout all your HTML?</p>
<p>Or do you just call .redbox something like .infobox that represents it's purpose rather than it's colour.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Bannatyne</title>
		<link>http://fwebde.com/css/css-best-practices/comment-page-1/#comment-1125</link>
		<dc:creator>Eric Bannatyne</dc:creator>
		<pubDate>Thu, 04 Feb 2010 15:34:07 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=1221#comment-1125</guid>
		<description>That&#039;s interesting. I just prefer each rule to have its own line, because that&#039;s just what I&#039;m used to, and it works perfectly fine for me. It really is just a matter of personal taste.</description>
		<content:encoded><![CDATA[<p>That's interesting. I just prefer each rule to have its own line, because that's just what I'm used to, and it works perfectly fine for me. It really is just a matter of personal taste.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amber Weinberg</title>
		<link>http://fwebde.com/css/css-best-practices/comment-page-1/#comment-1124</link>
		<dc:creator>Amber Weinberg</dc:creator>
		<pubDate>Thu, 04 Feb 2010 14:30:14 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=1221#comment-1124</guid>
		<description>Good article but I disagree with the organization tip. To me, putting everything on one line is more organized, cleaner and saves space. I can also find what I&#039;m looking for much faster as I don&#039;t have to scroll through an endless page with one rule on each line. It also makes the file size smaller. I think it&#039;s more of a personal prefer, as doing one rule per line instead of doing it all on one line would def slow down my workflow exponitially.</description>
		<content:encoded><![CDATA[<p>Good article but I disagree with the organization tip. To me, putting everything on one line is more organized, cleaner and saves space. I can also find what I'm looking for much faster as I don't have to scroll through an endless page with one rule on each line. It also makes the file size smaller. I think it's more of a personal prefer, as doing one rule per line instead of doing it all on one line would def slow down my workflow exponitially.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Veera</title>
		<link>http://fwebde.com/css/css-best-practices/comment-page-1/#comment-1122</link>
		<dc:creator>Veera</dc:creator>
		<pubDate>Thu, 04 Feb 2010 13:10:22 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=1221#comment-1122</guid>
		<description>yes. these are the basic rules that every CSS developer must follow.</description>
		<content:encoded><![CDATA[<p>yes. these are the basic rules that every CSS developer must follow.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
