<?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 Frameworks and the Anatomy of Web Design</title>
	<atom:link href="http://frontendbook.com/css-frameworks-and-the-anatomy-of-web-design/feed" rel="self" type="application/rss+xml" />
	<link>http://frontendbook.com/css-frameworks-and-the-anatomy-of-web-design</link>
	<description>UX, Mobile, Web and Product Development</description>
	<lastBuildDate>Sat, 17 Dec 2011 10:07:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: alex farguson</title>
		<link>http://frontendbook.com/css-frameworks-and-the-anatomy-of-web-design#comment-254</link>
		<dc:creator>alex farguson</dc:creator>
		<pubDate>Sun, 08 Mar 2009 07:56:35 +0000</pubDate>
		<guid isPermaLink="false">http://snofs.com/blog/?p=130#comment-254</guid>
		<description>This is nice. Thank you :D</description>
		<content:encoded><![CDATA[<p>This is nice. Thank you <img src='http://frontendbook.com/wp3/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mattias Hising</title>
		<link>http://frontendbook.com/css-frameworks-and-the-anatomy-of-web-design#comment-252</link>
		<dc:creator>Mattias Hising</dc:creator>
		<pubDate>Mon, 28 Apr 2008 20:08:42 +0000</pubDate>
		<guid isPermaLink="false">http://snofs.com/blog/?p=130#comment-252</guid>
		<description>Thanks for your great input Eric. I firmly believe we have to start using these libraries for any type of website in order to focus on the correct things (design, usability and interaction) instead of cross-browser css and hacks in order to achieve things over and over again.</description>
		<content:encoded><![CDATA[<p>Thanks for your great input Eric. I firmly believe we have to start using these libraries for any type of website in order to focus on the correct things (design, usability and interaction) instead of cross-browser css and hacks in order to achieve things over and over again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Ferraiuolo</title>
		<link>http://frontendbook.com/css-frameworks-and-the-anatomy-of-web-design#comment-253</link>
		<dc:creator>Eric Ferraiuolo</dc:creator>
		<pubDate>Mon, 28 Apr 2008 15:54:03 +0000</pubDate>
		<guid isPermaLink="false">http://snofs.com/blog/?p=130#comment-253</guid>
		<description>There have been a bunch of articles published on various blog recently touching on this topic.

It seems there is a great deal of people that feel CSS Frameworks are just too big and too much for small sites or single pages. I can see their arguments when thinking about a web- &quot;page&quot; or &quot;site&quot;, but not when it comes to a web-&quot;application&quot;. When developing an application I feel that a CSS and JavaScript framework are a must. I really like your point about adding a minimal amount of new, un-tested, code to the working stack and utilize these libraries as a base starting-point.

I have a single page &quot;site&quot;, my resume, online which I used the Blueprint CSS framework for; by stating with that it took me ~2 hours to develop the graphics and add my &lt; 100 lines of specific CSS; and I know it works well right away in modern browsers, which and CSS person should know is a huge plus!</description>
		<content:encoded><![CDATA[<p>There have been a bunch of articles published on various blog recently touching on this topic.</p>
<p>It seems there is a great deal of people that feel CSS Frameworks are just too big and too much for small sites or single pages. I can see their arguments when thinking about a web- &#8220;page&#8221; or &#8220;site&#8221;, but not when it comes to a web-&#8221;application&#8221;. When developing an application I feel that a CSS and JavaScript framework are a must. I really like your point about adding a minimal amount of new, un-tested, code to the working stack and utilize these libraries as a base starting-point.</p>
<p>I have a single page &#8220;site&#8221;, my resume, online which I used the Blueprint CSS framework for; by stating with that it took me ~2 hours to develop the graphics and add my &lt; 100 lines of specific CSS; and I know it works well right away in modern browsers, which and CSS person should know is a huge plus!</p>
]]></content:encoded>
	</item>
</channel>
</rss>


