<?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: 5 Rules To Write More Readable CSS Files</title>
	<atom:link href="http://woorkup.com/2009/10/18/5-rules-to-write-more-readable-css-files/feed/" rel="self" type="application/rss+xml" />
	<link>http://woorkup.com/2009/10/18/5-rules-to-write-more-readable-css-files/</link>
	<description>A fresh charge of  creativity</description>
	<lastBuildDate>Wed, 08 Sep 2010 18:40:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Emil</title>
		<link>http://woorkup.com/2009/10/18/5-rules-to-write-more-readable-css-files/#comment-9115</link>
		<dc:creator>Emil</dc:creator>
		<pubDate>Thu, 11 Mar 2010 04:35:29 +0000</pubDate>
		<guid isPermaLink="false">http://woorkup.com/?p=810#comment-9115</guid>
		<description>Great post, however CSS compressors are not recommended for SEO readability. I would rather format the css (i.e):

#menu ul {
	width:980px;
	margin:0 auto;
	padding:0;
}
#menu ul li {
	float:left;
	list-style:none;
	padding:131px 0 0;
}
#menu ul li a {
	display:block;
	height:43px;
	text-decoration:none;
	color:#fff;
	padding:10px 10px 0;
}

it&#039;s much easier for SEO than compressed CSS.

Thanks,
Emil</description>
		<content:encoded><![CDATA[<p>Great post, however CSS compressors are not recommended for SEO readability. I would rather format the css (i.e):</p>
<p>#menu ul {<br />
	width:980px;<br />
	margin:0 auto;<br />
	padding:0;<br />
}<br />
#menu ul li {<br />
	float:left;<br />
	list-style:none;<br />
	padding:131px 0 0;<br />
}<br />
#menu ul li a {<br />
	display:block;<br />
	height:43px;<br />
	text-decoration:none;<br />
	color:#fff;<br />
	padding:10px 10px 0;<br />
}</p>
<p>it&#8217;s much easier for SEO than compressed CSS.</p>
<p>Thanks,<br />
Emil</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Santosh</title>
		<link>http://woorkup.com/2009/10/18/5-rules-to-write-more-readable-css-files/#comment-2773</link>
		<dc:creator>Santosh</dc:creator>
		<pubDate>Mon, 16 Nov 2009 11:23:35 +0000</pubDate>
		<guid isPermaLink="false">http://woorkup.com/?p=810#comment-2773</guid>
		<description>I never knew that there is CSS compressor. It works like a miracle. Thanks a tonne Antonnio.</description>
		<content:encoded><![CDATA[<p>I never knew that there is CSS compressor. It works like a miracle. Thanks a tonne Antonnio.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wien</title>
		<link>http://woorkup.com/2009/10/18/5-rules-to-write-more-readable-css-files/#comment-2768</link>
		<dc:creator>wien</dc:creator>
		<pubDate>Mon, 16 Nov 2009 10:00:03 +0000</pubDate>
		<guid isPermaLink="false">http://woorkup.com/?p=810#comment-2768</guid>
		<description>nice post, very helpful, thanks</description>
		<content:encoded><![CDATA[<p>nice post, very helpful, thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WebDesignExpert.Me</title>
		<link>http://woorkup.com/2009/10/18/5-rules-to-write-more-readable-css-files/#comment-2672</link>
		<dc:creator>WebDesignExpert.Me</dc:creator>
		<pubDate>Sun, 15 Nov 2009 12:52:26 +0000</pubDate>
		<guid isPermaLink="false">http://woorkup.com/?p=810#comment-2672</guid>
		<description>You could also do efficient CSS using CSS shorthand properties:
http://www.456bereastreet.com/archive/200502/efficient_css_with_shorthand_properties/
http://www.dustindiaz.com/css-shorthand/

CSS compressor for fast loading and efficiency:
http://iceyboard.no-ip.org/projects/css_compressor
http://www.andy-roberts.net/software/csscompressor/index.html

CSS spirtes for faster loading:
http://net.tutsplus.com/videos/screencasts/exactly-how-to-use-css-sprites/
http://www.tutorial9.net/web-tutorials/building-faster-websites-with-css-sprites/</description>
		<content:encoded><![CDATA[<p>You could also do efficient CSS using CSS shorthand properties:<br />
<a href="http://www.456bereastreet.com/archive/200502/efficient_css_with_shorthand_properties/" rel="nofollow">http://www.456bereastreet.com/archive/200502/efficient_css_with_shorthand_properties/</a><br />
<a href="http://www.dustindiaz.com/css-shorthand/" rel="nofollow">http://www.dustindiaz.com/css-shorthand/</a></p>
<p>CSS compressor for fast loading and efficiency:<br />
<a href="http://iceyboard.no-ip.org/projects/css_compressor" rel="nofollow">http://iceyboard.no-ip.org/projects/css_compressor</a><br />
<a href="http://www.andy-roberts.net/software/csscompressor/index.html" rel="nofollow">http://www.andy-roberts.net/software/csscompressor/index.html</a></p>
<p>CSS spirtes for faster loading:<br />
<a href="http://net.tutsplus.com/videos/screencasts/exactly-how-to-use-css-sprites/" rel="nofollow">http://net.tutsplus.com/videos/screencasts/exactly-how-to-use-css-sprites/</a><br />
<a href="http://www.tutorial9.net/web-tutorials/building-faster-websites-with-css-sprites/" rel="nofollow">http://www.tutorial9.net/web-tutorials/building-faster-websites-with-css-sprites/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Ideas</title>
		<link>http://woorkup.com/2009/10/18/5-rules-to-write-more-readable-css-files/#comment-2467</link>
		<dc:creator>Web Ideas</dc:creator>
		<pubDate>Mon, 09 Nov 2009 10:06:26 +0000</pubDate>
		<guid isPermaLink="false">http://woorkup.com/?p=810#comment-2467</guid>
		<description>Thanks for lesson, great article!</description>
		<content:encoded><![CDATA[<p>Thanks for lesson, great article!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa Kerr</title>
		<link>http://woorkup.com/2009/10/18/5-rules-to-write-more-readable-css-files/#comment-2428</link>
		<dc:creator>Lisa Kerr</dc:creator>
		<pubDate>Sun, 08 Nov 2009 22:28:55 +0000</pubDate>
		<guid isPermaLink="false">http://woorkup.com/?p=810#comment-2428</guid>
		<description>Thanks Antonio! Any coding help is like a gift from heaven...</description>
		<content:encoded><![CDATA[<p>Thanks Antonio! Any coding help is like a gift from heaven&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ali Qayyum</title>
		<link>http://woorkup.com/2009/10/18/5-rules-to-write-more-readable-css-files/#comment-2419</link>
		<dc:creator>Ali Qayyum</dc:creator>
		<pubDate>Sun, 08 Nov 2009 17:32:32 +0000</pubDate>
		<guid isPermaLink="false">http://woorkup.com/?p=810#comment-2419</guid>
		<description>hi nice practice for me. i got idea ...i love your posts
keep posting like this, awesome cool</description>
		<content:encoded><![CDATA[<p>hi nice practice for me. i got idea &#8230;i love your posts<br />
keep posting like this, awesome cool</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://woorkup.com/2009/10/18/5-rules-to-write-more-readable-css-files/#comment-2358</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Sat, 07 Nov 2009 18:47:32 +0000</pubDate>
		<guid isPermaLink="false">http://woorkup.com/?p=810#comment-2358</guid>
		<description>A nice little round up there. I agree and practice all of these except #4 - &#039;Use extra spaces and tabulations to separate single properties from their values&#039;. I find reading CSS selectors that have dirty great gaps between their rules and values really difficult on the eyes.</description>
		<content:encoded><![CDATA[<p>A nice little round up there. I agree and practice all of these except #4 &#8211; &#8216;Use extra spaces and tabulations to separate single properties from their values&#8217;. I find reading CSS selectors that have dirty great gaps between their rules and values really difficult on the eyes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ピエールランリ・ラヴィン</title>
		<link>http://woorkup.com/2009/10/18/5-rules-to-write-more-readable-css-files/#comment-2091</link>
		<dc:creator>ピエールランリ・ラヴィン</dc:creator>
		<pubDate>Tue, 03 Nov 2009 15:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://woorkup.com/?p=810#comment-2091</guid>
		<description>Take it easy, but I think you should reconsider your post by web industries workers or ague a little more your steps. To my mind most of the steps you&#039;re citing are not possible.

From my experiences in web industries and web agencies:
You can simply forget about 1, 2 and 4:
1) Everyone likes to group properties by alphabets OR categories OR his/her own preferences
2) Any kind of  way to indent selectors will finish as exotic css files. Break line only if need be
3) Css should not be indenting as html.  css is more like queries than data descriptions.
4) It won&#039;t work, some developers will get a pain while developing the pages
5) It won&#039;t work, it will not be maintainable

Just make developers agree about using 3 and 5 and typically, it&#039;s
* Setting a short informative headers
* Grouping selectors by sections
* Grouping selectors with the same properties
* Only indenting the properties

Then the top of the top and the most boring is FINDING A FEW MINUTES to talk about editors:
* USE SPACE AS UNIT
* USE OPTIONS such as virtual wrap, virtual tab, tab space, reformat mix tabs, etc... so everyone can code in a way that doesn&#039;t hurt the neighboord. Yes they  can display the css in a way nearest to their but they didn&#039;t know it.

By default every developer thinks his config is the best in the world. His editor is not oriented team, it was configured to override any display that doesn&#039;t match Mr Smith the guru. You can come in a random company and say &quot;That&#039;s the way we should work&quot;, it won&#039;t work. Just explain a few requirements, give them liberties, talk about editors, and then everyone should be able to work anywhere with any members on the same basis. Evangelizing web is also evangelizing web related tools.

Actually, sorry wookup readers if I hurt you, we don&#039;t care how you like ordering the css properties as we don&#039;t care how you prefer chocolate than strawberry. A company or manager or leader just want you to be able and to enjoy working anywhere on any projects with any co-workers. That&#039;s all web development is about: team work !

Please bring Wookup higher ! ! ! ! 

Thanks and cheers</description>
		<content:encoded><![CDATA[<p>Take it easy, but I think you should reconsider your post by web industries workers or ague a little more your steps. To my mind most of the steps you&#8217;re citing are not possible.</p>
<p>From my experiences in web industries and web agencies:<br />
You can simply forget about 1, 2 and 4:<br />
1) Everyone likes to group properties by alphabets OR categories OR his/her own preferences<br />
2) Any kind of  way to indent selectors will finish as exotic css files. Break line only if need be<br />
3) Css should not be indenting as html.  css is more like queries than data descriptions.<br />
4) It won&#8217;t work, some developers will get a pain while developing the pages<br />
5) It won&#8217;t work, it will not be maintainable</p>
<p>Just make developers agree about using 3 and 5 and typically, it&#8217;s<br />
* Setting a short informative headers<br />
* Grouping selectors by sections<br />
* Grouping selectors with the same properties<br />
* Only indenting the properties</p>
<p>Then the top of the top and the most boring is FINDING A FEW MINUTES to talk about editors:<br />
* USE SPACE AS UNIT<br />
* USE OPTIONS such as virtual wrap, virtual tab, tab space, reformat mix tabs, etc&#8230; so everyone can code in a way that doesn&#8217;t hurt the neighboord. Yes they  can display the css in a way nearest to their but they didn&#8217;t know it.</p>
<p>By default every developer thinks his config is the best in the world. His editor is not oriented team, it was configured to override any display that doesn&#8217;t match Mr Smith the guru. You can come in a random company and say &#8220;That&#8217;s the way we should work&#8221;, it won&#8217;t work. Just explain a few requirements, give them liberties, talk about editors, and then everyone should be able to work anywhere with any members on the same basis. Evangelizing web is also evangelizing web related tools.</p>
<p>Actually, sorry wookup readers if I hurt you, we don&#8217;t care how you like ordering the css properties as we don&#8217;t care how you prefer chocolate than strawberry. A company or manager or leader just want you to be able and to enjoy working anywhere on any projects with any co-workers. That&#8217;s all web development is about: team work !</p>
<p>Please bring Wookup higher ! ! ! ! </p>
<p>Thanks and cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://woorkup.com/2009/10/18/5-rules-to-write-more-readable-css-files/#comment-1295</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Sun, 25 Oct 2009 19:24:22 +0000</pubDate>
		<guid isPermaLink="false">http://woorkup.com/?p=810#comment-1295</guid>
		<description>I thought the same thing about the icons. Assigning multiple classes for something like that is one of the best things about CSS.</description>
		<content:encoded><![CDATA[<p>I thought the same thing about the icons. Assigning multiple classes for something like that is one of the best things about CSS.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
