<?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 coding conventions</title>
	<atom:link href="http://www.phpied.com/css-coding-conventions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.phpied.com/css-coding-conventions/</link>
	<description>Stoyan&#039;s blog about &#60;a href=&#34;/category/xhtml&#34; class=&#34;tag-minor&#34;&#62;(x)html(5)&#60;/a&#62;, &#60;a href=&#34;/category/ajax&#34; class=&#34;tag-major&#34;&#62;ajax&#60;/a&#62;, &#60;a href=&#34;/category/bookmarklets&#34; class=&#34;tag-major&#34;&#62;bookmarklets&#60;/a&#62;, &#60;a href=&#34;/category/browsers&#34; class=&#34;tag-minor&#34;&#62;browsers&#60;/a&#62;, &#60;a href=&#34;/category/css&#34; class=&#34;tag-normal&#34;&#62;css&#60;/a&#62;, &#60;a href=&#34;/category/firebug&#34; class=&#34;tag-minor&#34;&#62;firebug&#60;/a&#62;, &#60;a href=&#34;/category/javascript&#34; class=&#34;tag-numero-uno&#34;&#62;javascript&#60;/a&#62;, &#60;a href=&#34;/category/json&#34; class=&#34;tag-normal&#34;&#62;json&#60;/a&#62;, &#60;a href=&#34;/category/mdb2&#34; class=&#34;tag-minor&#34;&#62;mdb2&#60;/a&#62;, &#60;a href=&#34;/category/mysql&#34; class=&#34;tag-normal&#34;&#62;mysql&#60;/a&#62;, &#60;a href=&#34;/category/pear&#34; class=&#34;tag-numero-uno&#34;&#62;pear&#60;/a&#62;, &#60;a href=&#34;/category/performance&#34; class=&#34;tag-major&#34;&#62;performance&#60;/a&#62;, &#60;a href=&#34;/category/php&#34; class=&#34;tag-numero-uno&#34;&#62;php&#60;/a&#62;, &#60;a href=&#34;/category/phpbb&#34; class=&#34;tag-major&#34;&#62;phpbb&#60;/a&#62;, &#60;a href=&#34;/category/tools&#34; class=&#34;tag-normal&#34;&#62;tools&#60;/a&#62;, &#60;a href=&#34;/category/yslow&#34; class=&#34;tag-minor&#34;&#62;yslow&#60;/a&#62;, &#60;a href=&#34;/category/yui&#34; class=&#34;tag-normal&#34;&#62;yui&#60;/a&#62;, &#60;a href=&#34;/category/writing&#34; class=&#34;tag-minor&#34;&#62;writing&#60;/a&#62;, &#60;a href=&#34;/category/music&#34; class=&#34;tag-major&#34;&#62;music&#60;/a&#62;,... &#60;a href=&#34;/category/life-and-everything&#34; class=&#34;tag-normal&#34;&#62;life and everything&#60;/a&#62;.</description>
	<lastBuildDate>Sat, 11 Feb 2012 14:07:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: CSS Coding Conventions &#124; Experi:mental</title>
		<link>http://www.phpied.com/css-coding-conventions/#comment-80513</link>
		<dc:creator>CSS Coding Conventions &#124; Experi:mental</dc:creator>
		<pubDate>Thu, 01 Dec 2011 09:00:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpied.com/css-coding-convensions/#comment-80513</guid>
		<description>[...] process I have been looking elsewhere too.LinksWordPress CSS Coding Standard &#8211; WordPress CodexCSS Coding Conventions &#8211; phpied5 Tips for WordPress Theme Developers &#8211; theme.fm This entry was posted in [...]</description>
		<content:encoded><![CDATA[<p>[...] process I have been looking elsewhere too.LinksWordPress CSS Coding Standard &#8211; WordPress CodexCSS Coding Conventions &#8211; phpied5 Tips for WordPress Theme Developers &#8211; theme.fm This entry was posted in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Free graphics, 3d, code snippets, PHP, HTML, JavaScript and more!</title>
		<link>http://www.phpied.com/css-coding-conventions/#comment-79923</link>
		<dc:creator>Free graphics, 3d, code snippets, PHP, HTML, JavaScript and more!</dc:creator>
		<pubDate>Sat, 19 Nov 2011 18:23:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpied.com/css-coding-convensions/#comment-79923</guid>
		<description>&lt;strong&gt;Free graphics, 3d, code snippets, PHP, HTML, JavaScript and more!...&lt;/strong&gt;

[...]CSS coding conventions / Stoyan&#039;s phpied.com[...]...</description>
		<content:encoded><![CDATA[<p><strong>Free graphics, 3d, code snippets, PHP, HTML, JavaScript and more!&#8230;</strong></p>
<p>[...]CSS coding conventions / Stoyan&#8217;s phpied.com[...]&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scrolling text</title>
		<link>http://www.phpied.com/css-coding-conventions/#comment-79232</link>
		<dc:creator>scrolling text</dc:creator>
		<pubDate>Sat, 05 Nov 2011 10:18:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpied.com/css-coding-convensions/#comment-79232</guid>
		<description>Its such as you learn my mind! You appear to understand so much approximately this, like you wrote the ebook in it or something. I believe that you can do with a few % to pressure the message house a little bit, but instead of that, this is magnificent blog. An excellent read. I&#039;ll definitely be back.</description>
		<content:encoded><![CDATA[<p>Its such as you learn my mind! You appear to understand so much approximately this, like you wrote the ebook in it or something. I believe that you can do with a few % to pressure the message house a little bit, but instead of that, this is magnificent blog. An excellent read. I&#8217;ll definitely be back.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Argon</title>
		<link>http://www.phpied.com/css-coding-conventions/#comment-79221</link>
		<dc:creator>Argon</dc:creator>
		<pubDate>Sat, 05 Nov 2011 02:27:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpied.com/css-coding-convensions/#comment-79221</guid>
		<description>Sorry completely disagree with the naming convention 

.footer-copyright  distracts far more then footerCopyright plus for people who copy and past try to double click on the first and then the second see what the difference is</description>
		<content:encoded><![CDATA[<p>Sorry completely disagree with the naming convention </p>
<p>.footer-copyright  distracts far more then footerCopyright plus for people who copy and past try to double click on the first and then the second see what the difference is</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wedding Thanks you</title>
		<link>http://www.phpied.com/css-coding-conventions/#comment-77981</link>
		<dc:creator>Wedding Thanks you</dc:creator>
		<pubDate>Sun, 19 Jun 2011 21:45:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpied.com/css-coding-convensions/#comment-77981</guid>
		<description>I quite agree with you mentioned, I think if css file is quite large, using shorthands can reduce the file size and improve performance. Having all opinion of that I already do the things you suggest.</description>
		<content:encoded><![CDATA[<p>I quite agree with you mentioned, I think if css file is quite large, using shorthands can reduce the file size and improve performance. Having all opinion of that I already do the things you suggest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What is the best way to organize CSS files? - Quora</title>
		<link>http://www.phpied.com/css-coding-conventions/#comment-77712</link>
		<dc:creator>What is the best way to organize CSS files? - Quora</dc:creator>
		<pubDate>Tue, 10 May 2011 21:07:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpied.com/css-coding-convensions/#comment-77712</guid>
		<description>[...] User Should also mention Less (http://lesscss.org/), and for coding conventions see this post : http://www.phpied.com/css-coding... or this http://meiert.com/en/blog/200805...As per usual: Pick your rules and stick to them.This [...]</description>
		<content:encoded><![CDATA[<p>[...] User Should also mention Less (<a href="http://lesscss.org/" rel="nofollow">http://lesscss.org/</a>), and for coding conventions see this post : <a href="http://www.phpied.com/css-coding.." rel="nofollow">http://www.phpied.com/css-coding..</a>. or this <a href="http://meiert.com/en/blog/200805...As" rel="nofollow">http://meiert.com/en/blog/200805&#8230;As</a> per usual: Pick your rules and stick to them.This [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the rasx() context &#187; Blog Archive &#187; @denisejacobs CSS Links</title>
		<link>http://www.phpied.com/css-coding-conventions/#comment-76945</link>
		<dc:creator>the rasx() context &#187; Blog Archive &#187; @denisejacobs CSS Links</dc:creator>
		<pubDate>Tue, 22 Mar 2011 15:35:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpied.com/css-coding-convensions/#comment-76945</guid>
		<description>[...] Stoyan Stefanov: “The important thing to remember is—it’s not that important what exactly is a chosen standard or convention, the most important is that there is one. The rest, the details, is just common sense, and since ‘the common sense is not common to everybody’, pick whatever makes sense for you.” [...]</description>
		<content:encoded><![CDATA[<p>[...] Stoyan Stefanov: “The important thing to remember is—it’s not that important what exactly is a chosen standard or convention, the most important is that there is one. The rest, the details, is just common sense, and since ‘the common sense is not common to everybody’, pick whatever makes sense for you.” [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terry Prothero</title>
		<link>http://www.phpied.com/css-coding-conventions/#comment-74305</link>
		<dc:creator>Terry Prothero</dc:creator>
		<pubDate>Sun, 24 Oct 2010 18:01:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpied.com/css-coding-convensions/#comment-74305</guid>
		<description>File size for a style sheet is an almost silly consideration given that it&#039;s a text file that takes up virtually no space.  Readability should be the primary concern.  I favor putting everything on one line provided that you keep the line length short.

You can do this by setting font family and some other standard settings on a more global level, such as in the body tag or on div tags that you know will encapsulate a number of others.  This way you don&#039;t have to so redundant.  I think that I would add a space after the semi-colon, and would also put a blank line or two between blocks of related items.  A comment here or there, probably wouldn&#039;t hurt either.

The issue of capitalization is an important one.  In my own code, I&#039;m all over the place on this and really need to get my act together.</description>
		<content:encoded><![CDATA[<p>File size for a style sheet is an almost silly consideration given that it&#8217;s a text file that takes up virtually no space.  Readability should be the primary concern.  I favor putting everything on one line provided that you keep the line length short.</p>
<p>You can do this by setting font family and some other standard settings on a more global level, such as in the body tag or on div tags that you know will encapsulate a number of others.  This way you don&#8217;t have to so redundant.  I think that I would add a space after the semi-colon, and would also put a blank line or two between blocks of related items.  A comment here or there, probably wouldn&#8217;t hurt either.</p>
<p>The issue of capitalization is an important one.  In my own code, I&#8217;m all over the place on this and really need to get my act together.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sriram</title>
		<link>http://www.phpied.com/css-coding-conventions/#comment-73966</link>
		<dc:creator>sriram</dc:creator>
		<pubDate>Mon, 30 Aug 2010 10:55:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpied.com/css-coding-convensions/#comment-73966</guid>
		<description>I wont accept the point,if you give spacing its gives readability,but at the same time it will increase the file size also.

For a instance..

Eg:
#header{
margin:10px;
background:red;
padding:10px;}
.
.
.
.


#footer{
margin:10px;
background:green;
padding:10px;}

Instead of writing one by one,if you write in single line and compare the CSS file size.The below example file size will be less.

Eg:
#header{margin:10px;background:red;padding:10px;}
.
.
.
#footer{margin:10px;background:green;padding:10px;}

if you write in single line and reduce the spaces then you can easily avoid the file size of the CSS.</description>
		<content:encoded><![CDATA[<p>I wont accept the point,if you give spacing its gives readability,but at the same time it will increase the file size also.</p>
<p>For a instance..</p>
<p>Eg:<br />
#header{<br />
margin:10px;<br />
background:red;<br />
padding:10px;}<br />
.<br />
.<br />
.<br />
.</p>
<p>#footer{<br />
margin:10px;<br />
background:green;<br />
padding:10px;}</p>
<p>Instead of writing one by one,if you write in single line and compare the CSS file size.The below example file size will be less.</p>
<p>Eg:<br />
#header{margin:10px;background:red;padding:10px;}<br />
.<br />
.<br />
.<br />
#footer{margin:10px;background:green;padding:10px;}</p>
<p>if you write in single line and reduce the spaces then you can easily avoid the file size of the CSS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.phpied.com/css-coding-conventions/#comment-72314</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Fri, 19 Feb 2010 19:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.phpied.com/css-coding-convensions/#comment-72314</guid>
		<description>I like that someone at least made an attempt to discuss CSS conventions, which was conveniently left out of all my formal training in college. Convention emphasis was always placed on things like VB.Net, Java, C++, PHP, etc....

I personally, am a fan of camel casing my IDs, classes, etc.  For those unfamiliar (really?), thisIsCamelCasing  or for a real world example &quot;#mainNavigation&quot;.  I find them just as easy to read, and much easier to type than using hyphens, and A LOT easier to type than using underscores.

A point people probably never considered is the ease of perusing text in a WYSIWYG&#039;s using naming conventions. Hyphens slow down your text-cursor when cruising a line of text because it stops at each hyphen, whereas it skips right over camelCasing. Minor convenience, but I find it invaluable.

I still use hyphens, but only to distinguish between a .class-subClass-subSubClass type of scenario.

By the way, I agree with you on the shorthand notation. Every once in a while you run into syntax you seldom see and wonder w.t.h. is going on. I have some exceptions, I use shorthand for margin:Top Right Bottom Left; and for border:1px solid #HHEEXX.

I don&#039;t put spaces after colons, only after semi-colons between styles in a single pair.</description>
		<content:encoded><![CDATA[<p>I like that someone at least made an attempt to discuss CSS conventions, which was conveniently left out of all my formal training in college. Convention emphasis was always placed on things like VB.Net, Java, C++, PHP, etc&#8230;.</p>
<p>I personally, am a fan of camel casing my IDs, classes, etc.  For those unfamiliar (really?), thisIsCamelCasing  or for a real world example &#8220;#mainNavigation&#8221;.  I find them just as easy to read, and much easier to type than using hyphens, and A LOT easier to type than using underscores.</p>
<p>A point people probably never considered is the ease of perusing text in a WYSIWYG&#8217;s using naming conventions. Hyphens slow down your text-cursor when cruising a line of text because it stops at each hyphen, whereas it skips right over camelCasing. Minor convenience, but I find it invaluable.</p>
<p>I still use hyphens, but only to distinguish between a .class-subClass-subSubClass type of scenario.</p>
<p>By the way, I agree with you on the shorthand notation. Every once in a while you run into syntax you seldom see and wonder w.t.h. is going on. I have some exceptions, I use shorthand for margin:Top Right Bottom Left; and for border:1px solid #HHEEXX.</p>
<p>I don&#8217;t put spaces after colons, only after semi-colons between styles in a single pair.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

