<?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"
	>
<channel>
	<title>Comments on: Treading Lightly with CSS Frameworks</title>
	<atom:link href="http://manwithnoblog.com/2007/09/09/treading-lightly-with-css-frameworks/feed/" rel="self" type="application/rss+xml" />
	<link>http://manwithnoblog.com/2007/09/09/treading-lightly-with-css-frameworks/</link>
	<description>Gary Barber rants on user experience, information architecture and the web industry.</description>
	<pubDate>Thu, 24 Jul 2008 14:10:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: David McDonald</title>
		<link>http://manwithnoblog.com/2007/09/09/treading-lightly-with-css-frameworks/#comment-2934</link>
		<dc:creator>David McDonald</dc:creator>
		<pubDate>Sat, 22 Sep 2007 00:50:29 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/2007/09/09/treading-lightly-with-css-frameworks/#comment-2934</guid>
		<description>I, too, save time on builds by using a basic 'templating' system that I have refined over the years.

What I find with a lot of these frameworks is that they try to be 'all things to all people', which leads to using more code than is necessary, so I tend to spend quite a bit of time actually removing unnecessary CSS and XHTML and rewriting.</description>
		<content:encoded><![CDATA[<p>I, too, save time on builds by using a basic &#8216;templating&#8217; system that I have refined over the years.</p>
<p>What I find with a lot of these frameworks is that they try to be &#8216;all things to all people&#8217;, which leads to using more code than is necessary, so I tend to spend quite a bit of time actually removing unnecessary CSS and XHTML and rewriting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashul Shah</title>
		<link>http://manwithnoblog.com/2007/09/09/treading-lightly-with-css-frameworks/#comment-2881</link>
		<dc:creator>Ashul Shah</dc:creator>
		<pubDate>Mon, 10 Sep 2007 16:27:34 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/2007/09/09/treading-lightly-with-css-frameworks/#comment-2881</guid>
		<description>We had a long discussion about this in the office today and it seems that unbeknown to us we are already using an in-house CSS framework or as you put it templated system - simply borne out of requiring a common standards based approach in building the CSS for sites using the single platform (the EdukaCMS) our collective agreement was a CSS framework is good but you need make sure it is used by all team members in all projects for it to work..</description>
		<content:encoded><![CDATA[<p>We had a long discussion about this in the office today and it seems that unbeknown to us we are already using an in-house CSS framework or as you put it templated system - simply borne out of requiring a common standards based approach in building the CSS for sites using the single platform (the EdukaCMS) our collective agreement was a CSS framework is good but you need make sure it is used by all team members in all projects for it to work..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Barber</title>
		<link>http://manwithnoblog.com/2007/09/09/treading-lightly-with-css-frameworks/#comment-2876</link>
		<dc:creator>Gary Barber</dc:creator>
		<pubDate>Sun, 09 Sep 2007 14:21:26 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/2007/09/09/treading-lightly-with-css-frameworks/#comment-2876</guid>
		<description>@sutto That's how I use my templates, all the basic layout and presentational elements are in place. Cuts hours of the time required for building a site. There is a grid, but not in the form as in Blueprint. You could even just standardise the elements and in doing so make them standards and accessibility compliant.</description>
		<content:encoded><![CDATA[<p>@sutto That&#8217;s how I use my templates, all the basic layout and presentational elements are in place. Cuts hours of the time required for building a site. There is a grid, but not in the form as in Blueprint. You could even just standardise the elements and in doing so make them standards and accessibility compliant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sutto</title>
		<link>http://manwithnoblog.com/2007/09/09/treading-lightly-with-css-frameworks/#comment-2875</link>
		<dc:creator>Sutto</dc:creator>
		<pubDate>Sun, 09 Sep 2007 14:12:05 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/2007/09/09/treading-lightly-with-css-frameworks/#comment-2875</guid>
		<description>I'm doing RailsRumble at the moment and used Blueprint to setup a basis quickly and easily - I personally feel it makes a world of a difference when your in a situation that involves rapid prototyping - I mean, I would of taken ages other wise to get anything near to what I had in 1 hour.

On the idea of going further - I think for some aspects, it can be useful - e.g. uni-form where standardizing the form markup. I find it helps give you something consistent to work with, even if its only the for the sake of development (and not for accessibility of others, even though thats important ;))</description>
		<content:encoded><![CDATA[<p>I&#8217;m doing RailsRumble at the moment and used Blueprint to setup a basis quickly and easily - I personally feel it makes a world of a difference when your in a situation that involves rapid prototyping - I mean, I would of taken ages other wise to get anything near to what I had in 1 hour.</p>
<p>On the idea of going further - I think for some aspects, it can be useful - e.g. uni-form where standardizing the form markup. I find it helps give you something consistent to work with, even if its only the for the sake of development (and not for accessibility of others, even though thats important ;))</p>
]]></content:encoded>
	</item>
</channel>
</rss>
