<?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: Leadership Institute &#8211; Website Strategies</title>
	<atom:link href="http://churchtechmatters.com/2006/10/08/leadership-institute-website-strategies/feed/" rel="self" type="application/rss+xml" />
	<link>http://churchtechmatters.com/2006/10/08/leadership-institute-website-strategies/</link>
	<description>A site for tech volunteers written by tech volunteers</description>
	<lastBuildDate>Thu, 11 Mar 2010 12:46:29 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Peter Schott</title>
		<link>http://churchtechmatters.com/2006/10/08/leadership-institute-website-strategies/comment-page-1/#comment-8105</link>
		<dc:creator>Peter Schott</dc:creator>
		<pubDate>Mon, 09 Oct 2006 16:10:25 +0000</pubDate>
		<guid isPermaLink="false">http://churchtechmatters.com/2006/10/08/leadership-institute-website-strategies/#comment-8105</guid>
		<description>I&#039;d love to see some more details on this post.  I&#039;ve been investigating using a CMS system for the church website redesign as it will give the capability to ministry owners to post their own news, events, and other items without needing someone to make the changes.  Sounds like there&#039;s some interesting discussion behind this post.

-Pete</description>
		<content:encoded><![CDATA[<p>I&#8217;d love to see some more details on this post.  I&#8217;ve been investigating using a CMS system for the church website redesign as it will give the capability to ministry owners to post their own news, events, and other items without needing someone to make the changes.  Sounds like there&#8217;s some interesting discussion behind this post.</p>
<p>-Pete</p>
]]></content:encoded>
	</item>
</channel>
</rss>
