<?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: blog as a delivery platform</title>
	<atom:link href="http://www.afhill.com/blog/blog-as-a-delivery-platform/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.afhill.com/blog/blog-as-a-delivery-platform/</link>
	<description>Reflections on online strategy, social media marketing, web accessibility and interactive design.</description>
	<lastBuildDate>Tue, 07 Feb 2012 22:14:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Tawana Roney</title>
		<link>http://www.afhill.com/blog/blog-as-a-delivery-platform/#comment-251693</link>
		<dc:creator>Tawana Roney</dc:creator>
		<pubDate>Mon, 06 Jun 2011 23:10:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.afhill.com/blog/2008/01/23/blog-as-a-delivery-platform/#comment-251693</guid>
		<description>I simply added your web site to my top picks. I love reading your posts. Thanks!</description>
		<content:encoded><![CDATA[<p>I simply added your web site to my top picks. I love reading your posts. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Too Long, Didn&#8217;t Read &#124; Krotscheck.net</title>
		<link>http://www.afhill.com/blog/blog-as-a-delivery-platform/#comment-13785</link>
		<dc:creator>Too Long, Didn&#8217;t Read &#124; Krotscheck.net</dc:creator>
		<pubDate>Sun, 27 Jan 2008 01:11:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.afhill.com/blog/2008/01/23/blog-as-a-delivery-platform/#comment-13785</guid>
		<description>[...] piece on the topic by another coworker, taking the topic to the next step and discussing the blog as a delivery platform. The third was my own struggle to even complete a post (you wouldn’t believe how many unfinished [...]</description>
		<content:encoded><![CDATA[<p>[...] piece on the topic by another coworker, taking the topic to the next step and discussing the blog as a delivery platform. The third was my own struggle to even complete a post (you wouldn’t believe how many unfinished [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Krotscheck</title>
		<link>http://www.afhill.com/blog/blog-as-a-delivery-platform/#comment-13698</link>
		<dc:creator>Michael Krotscheck</dc:creator>
		<pubDate>Wed, 23 Jan 2008 20:43:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.afhill.com/blog/2008/01/23/blog-as-a-delivery-platform/#comment-13698</guid>
		<description>I think your last paragraph hints at the real way of thinking about this: It&#039;s not about the blog, it&#039;s about the audience. A blog focusing on scientific research, for instance, will have an audience perfectly willing to slug through pages of research notes and citations. To contrast a community blog like wordpress or livejournal will cater to a much more casual group interested in text bites and rapidly consumed content.

As a result I also have different expectations between domain blogs and community blogs. The former has a domain, a &quot;brand&quot; as it were, and as a reader I am self selecting myself to be a part of that brand, and I expect it to adhere to that brand (which, if we&#039;re being O.P.E.N., also requires my input and participation). The latter of the two doesn&#039;t have a strong brand other than that of the umbrella company, and as a result I expect a much lower noise-to-signal ratio.</description>
		<content:encoded><![CDATA[<p>I think your last paragraph hints at the real way of thinking about this: It&#8217;s not about the blog, it&#8217;s about the audience. A blog focusing on scientific research, for instance, will have an audience perfectly willing to slug through pages of research notes and citations. To contrast a community blog like wordpress or livejournal will cater to a much more casual group interested in text bites and rapidly consumed content.</p>
<p>As a result I also have different expectations between domain blogs and community blogs. The former has a domain, a &#8220;brand&#8221; as it were, and as a reader I am self selecting myself to be a part of that brand, and I expect it to adhere to that brand (which, if we&#8217;re being O.P.E.N., also requires my input and participation). The latter of the two doesn&#8217;t have a strong brand other than that of the umbrella company, and as a result I expect a much lower noise-to-signal ratio.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

