<?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: CSS Property Order Convention</title>
	<atom:link href="http://blog.neatlysliced.com/2009/01/css-property-order-convention/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.neatlysliced.com/2009/01/css-property-order-convention/</link>
	<description>Bread was overrated.</description>
	<lastBuildDate>Wed, 28 Jul 2010 14:58:19 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tony White</title>
		<link>http://blog.neatlysliced.com/2009/01/css-property-order-convention/comment-page-1/#comment-10573</link>
		<dc:creator>Tony White</dc:creator>
		<pubDate>Fri, 16 Jan 2009 22:22:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.neatlysliced.com/?p=258#comment-10573</guid>
		<description>I just noticed firebug alphabetizes the properties.  I&#039;d say you&#039;re on to something. :)</description>
		<content:encoded><![CDATA[<p>I just noticed firebug alphabetizes the properties.  I&#8217;d say you&#8217;re on to something. <img src='http://blog.neatlysliced.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jennifer</title>
		<link>http://blog.neatlysliced.com/2009/01/css-property-order-convention/comment-page-1/#comment-10572</link>
		<dc:creator>Jennifer</dc:creator>
		<pubDate>Fri, 16 Jan 2009 16:48:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.neatlysliced.com/?p=258#comment-10572</guid>
		<description>I haven&#039;t seen too many suggestions about ordering within the selector - everyone seems to talk about the ordering of the selectors themselves. About a year ago, I read something about alphabetizing (the link is lost in the bowels of my mind). I tried it a few months ago and it works great for me. I recommended to my coworkers to do they same thing and it&#039;s helpful when we look at each other&#039;s code.

Bowman&#039;s suggestion is great. The reason Bowman&#039;s suggestion doesn&#039;t work for me is that it isn&#039;t intuitive for someone unfamiliar with that organization - which sometimes can be pretty much everyone besides yourself. Alphabetizing is something that&#039;s immediately noticed, because it has nothing to do with the semantics of what the property means. 

A large number of CSS developers still struggle with semantics in writing selector names &lt;strong&gt;and&lt;/strong&gt; what the properties themselves do or mean. I&#039;ve explain the difference between margin, border, padding, and width and their correlational consequences many times to the same individuals; it takes a while for those relations to &quot;click&quot;. So if the developer doesn&#039;t fully understand what position has to do with float, or what correlation width and padding might have, or why z-index and position rely on each other, grouping them together or adjacent to each other loses meaning. Then when they need to make an addition, it&#039;s randomly placed at the bottom.

So for me, alphabetical ordering works best. When I have to hand the code off, my ordering is meaningful regardless of the experience level of the developer.</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t seen too many suggestions about ordering within the selector &#8211; everyone seems to talk about the ordering of the selectors themselves. About a year ago, I read something about alphabetizing (the link is lost in the bowels of my mind). I tried it a few months ago and it works great for me. I recommended to my coworkers to do they same thing and it&#8217;s helpful when we look at each other&#8217;s code.</p>
<p>Bowman&#8217;s suggestion is great. The reason Bowman&#8217;s suggestion doesn&#8217;t work for me is that it isn&#8217;t intuitive for someone unfamiliar with that organization &#8211; which sometimes can be pretty much everyone besides yourself. Alphabetizing is something that&#8217;s immediately noticed, because it has nothing to do with the semantics of what the property means. </p>
<p>A large number of CSS developers still struggle with semantics in writing selector names <strong>and</strong> what the properties themselves do or mean. I&#8217;ve explain the difference between margin, border, padding, and width and their correlational consequences many times to the same individuals; it takes a while for those relations to &#8220;click&#8221;. So if the developer doesn&#8217;t fully understand what position has to do with float, or what correlation width and padding might have, or why z-index and position rely on each other, grouping them together or adjacent to each other loses meaning. Then when they need to make an addition, it&#8217;s randomly placed at the bottom.</p>
<p>So for me, alphabetical ordering works best. When I have to hand the code off, my ordering is meaningful regardless of the experience level of the developer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony White</title>
		<link>http://blog.neatlysliced.com/2009/01/css-property-order-convention/comment-page-1/#comment-10571</link>
		<dc:creator>Tony White</dc:creator>
		<pubDate>Fri, 16 Jan 2009 16:30:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.neatlysliced.com/?p=258#comment-10571</guid>
		<description>Good points.  Even if there isn&#039;t an industry standard yet, a personal standard is good to establish.  Doug Bowman published his preference for properties order, but he wasn&#039;t advocating it for everyone - just telling what his habits are.

http://stopdesign.com/log/2005/03/04/staying-organized.html

Have you noticed what any others have voiced about this?</description>
		<content:encoded><![CDATA[<p>Good points.  Even if there isn&#8217;t an industry standard yet, a personal standard is good to establish.  Doug Bowman published his preference for properties order, but he wasn&#8217;t advocating it for everyone &#8211; just telling what his habits are.</p>
<p><a href="http://stopdesign.com/log/2005/03/04/staying-organized.html" rel="nofollow">http://stopdesign.com/log/2005/03/04/staying-organized.html</a></p>
<p>Have you noticed what any others have voiced about this?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
