<?xml version="1.0" encoding="utf-8"?>	<rss version="2.0" 
		xmlns:content="http://purl.org/rss/1.0/modules/content/"
		xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	>
	<channel>
		<title><![CDATA[CSS - How to do it right]]></title>
		<link><![CDATA[http://www.bumpzee.com/lists/css-how-to-do-it-right/]]></link>
		<description><![CDATA[]]></description>
		<language>en-us</language>
		<pubDate>Thu, 26 Jan 2012 20:08:08 -0500</pubDate>
		<lastBuildDate>Thu, 26 Jan 2012 20:08:08 -0500</lastBuildDate>
		<image>
			<title><![CDATA[CSS - How to do it right]]></title>
			<link><![CDATA[http://www.bumpzee.com/lists/css-how-to-do-it-right/]]></link>
			<url><![CDATA[]]></url>
		</image>
		<item>
		<title><![CDATA[70 Expert Ideas For Better CSS Coding]]></title>
		<link><![CDATA[http://www.bumpzee.com/bookmarks/70-expert-ideas-for-better-css-coding/]]></link>
		<description><![CDATA[<a href="http://www.bumpzee.com/bookmarks/70-expert-ideas-for-better-css-coding/"><img src="http://www.bumpzee.com/users/bz/damienarlabosse-10421-med.jpg"></a><br/> <blockquote>
<p>CSS isn&rsquo;t always easy to deal with. Depending on your skills and your experience, CSS coding can sometimes become a nightmare, particularly if you aren&rsquo;t sure which selectors are actually being applied to document elements.</p>
</blockquote>
<br>
<div>Source: <a href="http://coding.smashingmagazine.com/2007/05/10/70-expert-ideas-for-better-css-coding/">coding.smashingmagazine.com</a> &rarr; | <a href="http://www.bumpzee.com/bookmarks/70-expert-ideas-for-better-css-coding/">&#8734; Permalink</a></div><br/><div>More About: <a href="http://www.bumpzee.com/tags/css/">css</a> </div>]]></description>
				<content:encoded><![CDATA[<a href="http://www.bumpzee.com/bookmarks/70-expert-ideas-for-better-css-coding/"><img src="http://www.bumpzee.com/users/bz/damienarlabosse-10421-med.jpg"></a><br/> <blockquote>
<p>CSS isn&rsquo;t always easy to deal with. Depending on your skills and your experience, CSS coding can sometimes become a nightmare, particularly if you aren&rsquo;t sure which selectors are actually being applied to document elements.</p>
</blockquote>
<br>
<div>Source: <a href="http://coding.smashingmagazine.com/2007/05/10/70-expert-ideas-for-better-css-coding/">coding.smashingmagazine.com</a> &rarr; | <a href="http://www.bumpzee.com/bookmarks/70-expert-ideas-for-better-css-coding/">&#8734; Permalink</a></div><br/><div>More About: <a href="http://www.bumpzee.com/tags/css/">css</a> </div>]]></content:encoded>
		<comments><![CDATA[]]></comments>
		<pubDate><![CDATA[Thu, 26 Jan 2012 20:08:08 -0500]]></pubDate>
		<guid isPermaLink="true"><![CDATA[http://www.bumpzee.com/bookmarks/70-expert-ideas-for-better-css-coding/]]></guid>			
		<author><![CDATA[damienarlabosse]]></author>
	</item>
		<item>
		<title><![CDATA[LESS CSS Preprocessor]]></title>
		<link><![CDATA[http://www.bumpzee.com/bookmarks/less-css-preprocessor/]]></link>
		<description><![CDATA[<a href="http://www.bumpzee.com/bookmarks/less-css-preprocessor/"><img src="http://www.bumpzee.com/thumbs/b9aae867664c83176078b759e05aa886.jpg"></a><br/> <blockquote>
<p>A big problem we always have when we create a complex website is organizing the CSS properly. We add comments, we split it into files but the stylesheets still get pretty big if the project is very complex. Not only that but there are also a lot of browser specific CSS properties (such as -moz-border-radius) which make changing something (like the border-radius) very difficult. Well, there is something out there that can help us organize better and it is called LESS. The LESS CSS preprocessor has been out for some time and is well known by only a few developers. It basically enlarges the limits imposed by CSS&rsquo;s simplicity and allows the code to be compiled into &ldquo;real CSS&rdquo;. The coding style of LESS was thought to be a simplified but extensive variant of CSS so regular CSS code writers wouldn&rsquo;t need too much time migrating to this tool.</p>
</blockquote>
<br>
<div>Source: <a href="http://mbe.ro/2011/09/14/less-css-preprocessor-can-help-you-organize-your-css-better/">mbe.ro</a> &rarr; | <a href="http://www.bumpzee.com/bookmarks/less-css-preprocessor/">&#8734; Permalink</a></div><br/><div>More About: <a href="http://www.bumpzee.com/tags/css/">css</a> </div>]]></description>
				<content:encoded><![CDATA[<a href="http://www.bumpzee.com/bookmarks/less-css-preprocessor/"><img src="http://www.bumpzee.com/thumbs/b9aae867664c83176078b759e05aa886.jpg"></a><br/> <blockquote>
<p>A big problem we always have when we create a complex website is organizing the CSS properly. We add comments, we split it into files but the stylesheets still get pretty big if the project is very complex. Not only that but there are also a lot of browser specific CSS properties (such as -moz-border-radius) which make changing something (like the border-radius) very difficult. Well, there is something out there that can help us organize better and it is called LESS. The LESS CSS preprocessor has been out for some time and is well known by only a few developers. It basically enlarges the limits imposed by CSS&rsquo;s simplicity and allows the code to be compiled into &ldquo;real CSS&rdquo;. The coding style of LESS was thought to be a simplified but extensive variant of CSS so regular CSS code writers wouldn&rsquo;t need too much time migrating to this tool.</p>
</blockquote>
<br>
<div>Source: <a href="http://mbe.ro/2011/09/14/less-css-preprocessor-can-help-you-organize-your-css-better/">mbe.ro</a> &rarr; | <a href="http://www.bumpzee.com/bookmarks/less-css-preprocessor/">&#8734; Permalink</a></div><br/><div>More About: <a href="http://www.bumpzee.com/tags/css/">css</a> </div>]]></content:encoded>
		<comments><![CDATA[]]></comments>
		<pubDate><![CDATA[Thu, 26 Jan 2012 19:54:54 -0500]]></pubDate>
		<guid isPermaLink="true"><![CDATA[http://www.bumpzee.com/bookmarks/less-css-preprocessor/]]></guid>			
		<author><![CDATA[damienarlabosse]]></author>
	</item>
		<item>
		<title><![CDATA[Book - Scalable and Modular Architecture for CSS]]></title>
		<link><![CDATA[http://www.bumpzee.com/bookmarks/book-scalable-and-modular-architecture-for-css/]]></link>
		<description><![CDATA[<a href="http://www.bumpzee.com/bookmarks/book-scalable-and-modular-architecture-for-css/"><img src="http://www.bumpzee.com/thumbs/5af2e835ac0f4d5a20221013521339e4.jpg"></a><br/> 
<br>
<div>Source: <a href="http://smacss.com/book/">smacss.com</a> &rarr; | <a href="http://www.bumpzee.com/bookmarks/book-scalable-and-modular-architecture-for-css/">&#8734; Permalink</a></div><br/><div>More About: <a href="http://www.bumpzee.com/tags/css/">css</a> </div>]]></description>
				<content:encoded><![CDATA[<a href="http://www.bumpzee.com/bookmarks/book-scalable-and-modular-architecture-for-css/"><img src="http://www.bumpzee.com/thumbs/5af2e835ac0f4d5a20221013521339e4.jpg"></a><br/> 
<br>
<div>Source: <a href="http://smacss.com/book/">smacss.com</a> &rarr; | <a href="http://www.bumpzee.com/bookmarks/book-scalable-and-modular-architecture-for-css/">&#8734; Permalink</a></div><br/><div>More About: <a href="http://www.bumpzee.com/tags/css/">css</a> </div>]]></content:encoded>
		<comments><![CDATA[]]></comments>
		<pubDate><![CDATA[Thu, 26 Jan 2012 19:51:07 -0500]]></pubDate>
		<guid isPermaLink="true"><![CDATA[http://www.bumpzee.com/bookmarks/book-scalable-and-modular-architecture-for-css/]]></guid>			
		<author><![CDATA[damienarlabosse]]></author>
	</item>
		</channel>
	</rss>
	