<?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: A New Workflow for Web Designers</title>
	<atom:link href="http://www.pathf.com/blogs/2008/07/a-new-workflow-for-web-designers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2008/07/a-new-workflow-for-web-designers/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Fri, 09 Jan 2009 08:52:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: uxdesign.com</title>
		<link>http://www.pathf.com/blogs/2008/07/a-new-workflow-for-web-designers/#comment-2289</link>
		<dc:creator>uxdesign.com</dc:creator>
		<pubDate>Sat, 05 Jul 2008 16:21:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=999#comment-2289</guid>
		<description>The point that desktop tools will need to adapt to a growing web-as-software-platform paradigm, is one easy to agree with. Though I'd say that that democratization of web production and content publication cuts both ways: generally diminishing quality, while allowing the "asses" (masses ;-) their say.

For "It's easier, and better web design practice to get something online quickly, and tweak, or manage your design as it grows." This, for me, is just lack of experience: ignorance of the interdependencies between elements (purpose, use, visual design, interaction design, IA/content organization, etc. etc.). Best web design practice is to plan what you build, so to design for expansion. Otherwise a wild weed grows organically and loses the sense clarity and organization necessary for trust, which is indispensable to good communication. This for the same reason you build nothing else this way: not a house, shed, or even bird house. Plan, design, produce, evaluate. Rinse and repeat.</description>
		<content:encoded><![CDATA[<p>The point that desktop tools will need to adapt to a growing web-as-software-platform paradigm, is one easy to agree with. Though I&#8217;d say that that democratization of web production and content publication cuts both ways: generally diminishing quality, while allowing the &#8220;asses&#8221; (masses <img src='http://www.pathf.com/blogs/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> their say.</p>
<p>For &#8220;It&#8217;s easier, and better web design practice to get something online quickly, and tweak, or manage your design as it grows.&#8221; This, for me, is just lack of experience: ignorance of the interdependencies between elements (purpose, use, visual design, interaction design, IA/content organization, etc. etc.). Best web design practice is to plan what you build, so to design for expansion. Otherwise a wild weed grows organically and loses the sense clarity and organization necessary for trust, which is indispensable to good communication. This for the same reason you build nothing else this way: not a house, shed, or even bird house. Plan, design, produce, evaluate. Rinse and repeat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T.J.</title>
		<link>http://www.pathf.com/blogs/2008/07/a-new-workflow-for-web-designers/#comment-2259</link>
		<dc:creator>T.J.</dc:creator>
		<pubDate>Wed, 02 Jul 2008 15:13:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=999#comment-2259</guid>
		<description>Haven't finished reading your article, but I think you mean "masses", not "asses" in the first paragraph.  Although "assess" does give it nice humorous touch.</description>
		<content:encoded><![CDATA[<p>Haven&#8217;t finished reading your article, but I think you mean &#8220;masses&#8221;, not &#8220;asses&#8221; in the first paragraph.  Although &#8220;assess&#8221; does give it nice humorous touch.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
