<?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: Style guides and UI implementation: Part 2</title>
	<atom:link href="http://www.purecaffeine.com/2009/11/style-guides-and-ui-implementation-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.purecaffeine.com/2009/11/style-guides-and-ui-implementation-part-2/</link>
	<description>Interaction experience design blog - web, social, gov 2.0</description>
	<lastBuildDate>Wed, 28 Jul 2010 10:53:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nathanael Boehm</title>
		<link>http://www.purecaffeine.com/2009/11/style-guides-and-ui-implementation-part-2/comment-page-1/#comment-3344</link>
		<dc:creator>Nathanael Boehm</dc:creator>
		<pubDate>Fri, 11 Dec 2009 22:35:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.purecaffeine.com/?p=501#comment-3344</guid>
		<description>I don&#039;t believe style guides are as important for small sites delivered by smaller agencies for smaller companies. Style guides are really for where there are a lot of people involved in various aspects of communications, design development and publishing over a period of time with a substantial product where if not implemented correctly can take years to roll out simple brand tweaks. Riding a miniature toy ATV with two controls - throttle and steering - is a bit different from piloting an F-16 fighter jet. That&#039;s when it&#039;s important to have those manuals around so people can get a picture of the style that might not be as easily determined as with a quick scan of a 5-page $5k website.

Nonetheless, even in those cases it still would be nice to have a style guide because inevitably someone else will come along to maintain it within the 2-3 lifecycle of that site and introduce new design elements that don&#039;t align with the beautiful original brand.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t believe style guides are as important for small sites delivered by smaller agencies for smaller companies. Style guides are really for where there are a lot of people involved in various aspects of communications, design development and publishing over a period of time with a substantial product where if not implemented correctly can take years to roll out simple brand tweaks. Riding a miniature toy ATV with two controls &#8211; throttle and steering &#8211; is a bit different from piloting an F-16 fighter jet. That&#8217;s when it&#8217;s important to have those manuals around so people can get a picture of the style that might not be as easily determined as with a quick scan of a 5-page $5k website.</p>
<p>Nonetheless, even in those cases it still would be nice to have a style guide because inevitably someone else will come along to maintain it within the 2-3 lifecycle of that site and introduce new design elements that don&#8217;t align with the beautiful original brand.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cre8ive Commando</title>
		<link>http://www.purecaffeine.com/2009/11/style-guides-and-ui-implementation-part-2/comment-page-1/#comment-3314</link>
		<dc:creator>Cre8ive Commando</dc:creator>
		<pubDate>Fri, 11 Dec 2009 12:50:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.purecaffeine.com/?p=501#comment-3314</guid>
		<description>Great post Nathanael, it&#039;s packed with info :-)

But what I have found working as a web designer in a small company on a tight budget with short deadlines is that we simply don&#039;t have the time to create a comprehensive style guide. As a web designer I am basically the HTML coder, CSS writer and UI designer all in one.

Would be great to have the time to plan out things nicely.</description>
		<content:encoded><![CDATA[<p>Great post Nathanael, it&#8217;s packed with info :-)</p>
<p>But what I have found working as a web designer in a small company on a tight budget with short deadlines is that we simply don&#8217;t have the time to create a comprehensive style guide. As a web designer I am basically the HTML coder, CSS writer and UI designer all in one.</p>
<p>Would be great to have the time to plan out things nicely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathanael Boehm</title>
		<link>http://www.purecaffeine.com/2009/11/style-guides-and-ui-implementation-part-2/comment-page-1/#comment-2409</link>
		<dc:creator>Nathanael Boehm</dc:creator>
		<pubDate>Mon, 30 Nov 2009 11:46:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.purecaffeine.com/?p=501#comment-2409</guid>
		<description>I should also have mentioned that style guides should be an extension of existing corporate, brand and product style guides - not something developed in isolation or from scratch.</description>
		<content:encoded><![CDATA[<p>I should also have mentioned that style guides should be an extension of existing corporate, brand and product style guides &#8211; not something developed in isolation or from scratch.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
