<?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: Making the most of the web, right now</title>
	<atom:link href="http://benwerd.com/2009/06/making-the-most-of-the-web-right-now/feed/" rel="self" type="application/rss+xml" />
	<link>http://benwerd.com/2009/06/making-the-most-of-the-web-right-now/</link>
	<description></description>
	<lastBuildDate>Mon, 15 Mar 2010 19:24:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: alevin</title>
		<link>http://benwerd.com/2009/06/making-the-most-of-the-web-right-now/comment-page-1/#comment-25703</link>
		<dc:creator>alevin</dc:creator>
		<pubDate>Mon, 06 Jul 2009 21:38:11 +0000</pubDate>
		<guid isPermaLink="false">http://benwerd.com/2009/06/making-the-most-of-the-web-right-now/#comment-25703</guid>
		<description>Well said.  A related point is to consider the evolutionary path for a type of site.  For example, blog communities often start with a single-author blog, and later evolve to multi-author, and then multi-author with community contribution and reputation.  Forums are best with the smallest number of starting topics, and then branch out as the community grows. So, start with the smallest number of features that meet the core needs of the starting user community in the simplest, most understandable way, and be prepared for growth paths that take you the next steps.</description>
		<content:encoded><![CDATA[<p>Well said.  A related point is to consider the evolutionary path for a type of site.  For example, blog communities often start with a single-author blog, and later evolve to multi-author, and then multi-author with community contribution and reputation.  Forums are best with the smallest number of starting topics, and then branch out as the community grows. So, start with the smallest number of features that meet the core needs of the starting user community in the simplest, most understandable way, and be prepared for growth paths that take you the next steps.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
