<?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 Ethics Every Designer Should Have</title>
	<atom:link href="http://www.noupe.com/css/9-css-ethics-every-designer-should-have.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.noupe.com/css/9-css-ethics-every-designer-should-have.html</link>
	<description>The Curious Side of Smashing Magazine</description>
	<lastBuildDate>Sun, 12 Feb 2012 05:22:32 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: weboz.iam</title>
		<link>http://www.noupe.com/css/9-css-ethics-every-designer-should-have.html/comment-page-1#comment-25639</link>
		<dc:creator>weboz.iam</dc:creator>
		<pubDate>Mon, 13 Oct 2008 00:29:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.noupe.com/how-tos/the-9-css-ethics-every-designer-should-have.html#comment-25639</guid>
		<description>I agree with most of these, but this one about breaking stylesheets into few files I can&#039;t agree. Just, when you&#039;re doing a bigger website with few thousand visitors, it&#039;s pretty much important not to make too many HTTP requests..</description>
		<content:encoded><![CDATA[<p>I agree with most of these, but this one about breaking stylesheets into few files I can&#8217;t agree. Just, when you&#8217;re doing a bigger website with few thousand visitors, it&#8217;s pretty much important not to make too many HTTP requests..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Collins</title>
		<link>http://www.noupe.com/css/9-css-ethics-every-designer-should-have.html/comment-page-1#comment-11244</link>
		<dc:creator>Dan Collins</dc:creator>
		<pubDate>Thu, 10 Jul 2008 20:49:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.noupe.com/how-tos/the-9-css-ethics-every-designer-should-have.html#comment-11244</guid>
		<description>Great tips!
Thankyou very much!</description>
		<content:encoded><![CDATA[<p>Great tips!<br />
Thankyou very much!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shine</title>
		<link>http://www.noupe.com/css/9-css-ethics-every-designer-should-have.html/comment-page-1#comment-9943</link>
		<dc:creator>Shine</dc:creator>
		<pubDate>Thu, 03 Jul 2008 08:09:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.noupe.com/how-tos/the-9-css-ethics-every-designer-should-have.html#comment-9943</guid>
		<description>Great article! Thank you</description>
		<content:encoded><![CDATA[<p>Great article! Thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Martin</title>
		<link>http://www.noupe.com/css/9-css-ethics-every-designer-should-have.html/comment-page-1#comment-9837</link>
		<dc:creator>Eric Martin</dc:creator>
		<pubDate>Wed, 02 Jul 2008 16:55:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.noupe.com/how-tos/the-9-css-ethics-every-designer-should-have.html#comment-9837</guid>
		<description>Nice article, thanks!

I&#039;d never thought about doing #1 - seems like a good idea.

I switched to #3 a while ago and wouldn&#039;t want to go back to putting every element on a separate line.

I used #4 for a work project and I have to say, I&#039;m not a big fan. Mainly because it increases the number of server request and considering styles can bleed across functional uses, it can be difficult to organize correctly.

#8 is a good idea. I tend to group mine first by HTML elements (div, p, table, etc.) then according to the page layout.</description>
		<content:encoded><![CDATA[<p>Nice article, thanks!</p>
<p>I&#8217;d never thought about doing #1 &#8211; seems like a good idea.</p>
<p>I switched to #3 a while ago and wouldn&#8217;t want to go back to putting every element on a separate line.</p>
<p>I used #4 for a work project and I have to say, I&#8217;m not a big fan. Mainly because it increases the number of server request and considering styles can bleed across functional uses, it can be difficult to organize correctly.</p>
<p>#8 is a good idea. I tend to group mine first by HTML elements (div, p, table, etc.) then according to the page layout.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nikos</title>
		<link>http://www.noupe.com/css/9-css-ethics-every-designer-should-have.html/comment-page-1#comment-4247</link>
		<dc:creator>nikos</dc:creator>
		<pubDate>Thu, 01 May 2008 14:09:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.noupe.com/how-tos/the-9-css-ethics-every-designer-should-have.html#comment-4247</guid>
		<description>For me the best rule is number 6. Due to my day job (SEO) I am checking lots of time checking on websites and so far I havent seen a CSS file using a comment with all the color&#039;s values. Is a simple idea which can save a lot of time...

Thanks
Nikos</description>
		<content:encoded><![CDATA[<p>For me the best rule is number 6. Due to my day job (SEO) I am checking lots of time checking on websites and so far I havent seen a CSS file using a comment with all the color&#8217;s values. Is a simple idea which can save a lot of time&#8230;</p>
<p>Thanks<br />
Nikos</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Sinclair</title>
		<link>http://www.noupe.com/css/9-css-ethics-every-designer-should-have.html/comment-page-1#comment-3818</link>
		<dc:creator>John Sinclair</dc:creator>
		<pubDate>Tue, 22 Apr 2008 18:12:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.noupe.com/how-tos/the-9-css-ethics-every-designer-should-have.html#comment-3818</guid>
		<description>Item #3 -- one line is easy to read if your text editor or CSS editor gives you syntax coloring. But if I&#039;m browsing style sheets on the web it is harder to glance and understand.
Item #4 -- multiple imported stylesheets are harder to maintain and I find I can lose track of cascades and inheritances.
Items #1 and #2 -- I employ. The slight overhead associated with verbose commenting is outweighed by the maintainability. And I always assume someone else will someday work with my legacy code.
#9 -- class names such as .floatLeft and .center are simple, obvious, and expedient. They are best used in tags, not divs, For example, &lt;img class=&quot;alignRight&quot; and &lt;div class=&quot;menu&quot; both are descriptive.
Good article. A good dialog to start.</description>
		<content:encoded><![CDATA[<p>Item #3 &#8212; one line is easy to read if your text editor or CSS editor gives you syntax coloring. But if I&#8217;m browsing style sheets on the web it is harder to glance and understand.<br />
Item #4 &#8212; multiple imported stylesheets are harder to maintain and I find I can lose track of cascades and inheritances.<br />
Items #1 and #2 &#8212; I employ. The slight overhead associated with verbose commenting is outweighed by the maintainability. And I always assume someone else will someday work with my legacy code.<br />
#9 &#8212; class names such as .floatLeft and .center are simple, obvious, and expedient. They are best used in tags, not divs, For example, &lt;img class=&#8221;alignRight&#8221; and &lt;div class=&#8221;menu&#8221; both are descriptive.<br />
Good article. A good dialog to start.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

