<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Modularity &#038; Design Hierarchy</title>
	<link>http://www.nathancurtis.com/2007/07/06/design-hierarchy/</link>
	<description></description>
	<pubDate>Tue, 07 Sep 2010 14:09:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: nathancurtis.com &#187; Blog Archive &#187; Pattern Library vs. Component Library: What's the Diff?</title>
		<link>http://www.nathancurtis.com/2007/07/06/design-hierarchy/#comment-84</link>
		<author>nathancurtis.com &#187; Blog Archive &#187; Pattern Library vs. Component Library: What's the Diff?</author>
		<pubDate>Fri, 22 Feb 2008 04:37:23 +0000</pubDate>
		<guid>http://www.nathancurtis.com/2007/07/06/design-hierarchy/#comment-84</guid>
		<description>[...] assets to quickly get started in coding the solution; Components (ideally) manifest themselves modularly within the overall base of reference code for the [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] assets to quickly get started in coding the solution; Components (ideally) manifest themselves modularly within the overall base of reference code for the [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nathancurtis.com &#187; Blog Archive &#187; All For One? Or One For All?</title>
		<link>http://www.nathancurtis.com/2007/07/06/design-hierarchy/#comment-7</link>
		<author>nathancurtis.com &#187; Blog Archive &#187; All For One? Or One For All?</author>
		<pubDate>Sun, 29 Jul 2007 21:38:01 +0000</pubDate>
		<guid>http://www.nathancurtis.com/2007/07/06/design-hierarchy/#comment-7</guid>
		<description>[...] better yet, think about creating a deliverable environment that leverages modularity. Once you go modular, it&#8217;s increasingly easy to reuse - and maintain over time - a collection [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] better yet, think about creating a deliverable environment that leverages modularity. Once you go modular, it&#8217;s increasingly easy to reuse - and maintain over time - a collection [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nathancurtis.com &#187; Blog Archive &#187; Why Modularity Matters</title>
		<link>http://www.nathancurtis.com/2007/07/06/design-hierarchy/#comment-3</link>
		<author>nathancurtis.com &#187; Blog Archive &#187; Why Modularity Matters</author>
		<pubDate>Fri, 06 Jul 2007 03:38:25 +0000</pubDate>
		<guid>http://www.nathancurtis.com/2007/07/06/design-hierarchy/#comment-3</guid>
		<description>[...] Modularity provides a range of benefits and addresses many drawbacks of a typical documentation process. Useful for many UX staff members - not just your typical IA - it’s benefits increase alongside increases in team size, project scale, project duration, and more. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Modularity provides a range of benefits and addresses many drawbacks of a typical documentation process. Useful for many UX staff members - not just your typical IA - it’s benefits increase alongside increases in team size, project scale, project duration, and more. [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
