<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>PhilanthroMedia &#187; blogging</title>
	<atom:link href="http://www.philanthromedia.com/tag/blogging/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.philanthromedia.com</link>
	<description>Advancing Ideas that Matter</description>
	<lastBuildDate>Wed, 19 Oct 2011 15:37:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>To Blog or Not To Blog?</title>
		<link>http://www.philanthromedia.com/2008/07/23/to-blog-or-not-to-blog/</link>
		<comments>http://www.philanthromedia.com/2008/07/23/to-blog-or-not-to-blog/#comments</comments>
		<pubDate>Wed, 23 Jul 2008 17:06:54 +0000</pubDate>
		<dc:creator>Susan Herr</dc:creator>
				<category><![CDATA[2.0 Tools]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[web 2.0]]></category>

		<guid isPermaLink="false">http://www.philanthromedia.com/newsite/?p=62</guid>
		<description><![CDATA[PhilanthroMedia began our work in the world of new media by establishing PhilanthroMedia.org in August 2007.  Since then we’ve produced daily blog content that syndicates to more than 70 community foundations.
More than 450 posts later, we’ve learned a number of valuable lessons about the value of blogging that make us uniquely qualified to guide our [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.philanthromedia.com/wp-content/uploads/2008/07/Blog.jpg"><img class="alignleft size-full wp-image-125" style="margin-left: 4px; margin-right: 4px;" title="Blog" src="http://www.philanthromedia.com/wp-content/uploads/2008/07/Blog.jpg" alt="" width="255" height="153" /></a>PhilanthroMedia began our work in the world of new media by establishing <a href="http://www.philanthromedia.org">PhilanthroMedia.org</a> in August 2007.  Since then we’ve produced daily blog content that syndicates to more than 70 community foundations.</p>
<p>More than 450 posts later, we’ve learned a number of valuable lessons about the value of blogging that make us uniquely qualified to guide our clients in answering the questions “to blog or not to blog?  At a high level:</p>
<p>1.  -<strong>The Blog Monster is Voracious!</strong> In order to keep your content fresh, and to keep readers returning, you have to post regularly.  If you are going to host a blog as part of your communications strategy, be sure you understand clearly why you are making this move.</p>
<p>2.  -<strong>Blog Posts are (Relatively) Easy to Write</strong>.  One of the best things about blogging is that brevity is expected.  When you come up with a great insight, you knock out three paragraphs about it and see if anyone gives a flying flip.  If they do, you might want to spend more time fleshing it out.</p>
<p>3.  <strong>-Blogs Increase Your Visibility on Google</strong>.  Try to understand how Google archives your web and blog content and your head may fall off.  Those guys aren’t bazillionaires because what they do is intellectually accessible by the likes of mere mortals.  But two years of posting has shown us the results &#8212; more posts pop up when you use both blogs to advance ideas and make them easy for others to pick up on.</p>
<p>At Pm, we haven’t gone deep into the science of blogs &#8212; but we have learned the pros and cons of how they can be used as part of a broader strategy &#8212; info we would love to share if with organizations aggressively advancing ideas that matter.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.philanthromedia.com/2008/07/23/to-blog-or-not-to-blog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

