<?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: 5 non-technical reasons your church or charity needs to consider using Google Aps</title>
	<atom:link href="http://healyourchurchwebsite.com/2008/03/05/5-non-technical-reasons-your-church-or-charity-needs-to-consider-using-google-aps/feed/" rel="self" type="application/rss+xml" />
	<link>http://healyourchurchwebsite.com/2008/03/05/5-non-technical-reasons-your-church-or-charity-needs-to-consider-using-google-aps/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=5-non-technical-reasons-your-church-or-charity-needs-to-consider-using-google-aps</link>
	<description>Teaching, rebuking, correcting &#38; training in righteous web design.</description>
	<lastBuildDate>Mon, 26 Sep 2011 02:56:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: 5 Things Churches and Charities can learn from Google &#187; Heal Your Church WebSite</title>
		<link>http://healyourchurchwebsite.com/2008/03/05/5-non-technical-reasons-your-church-or-charity-needs-to-consider-using-google-aps/comment-page-1/#comment-4191</link>
		<dc:creator>5 Things Churches and Charities can learn from Google &#187; Heal Your Church WebSite</dc:creator>
		<pubDate>Fri, 10 Oct 2008 14:19:51 +0000</pubDate>
		<guid isPermaLink="false">http://healyourchurchwebsite.com/2008/03/05/5-non-technical-reasons-your-church-or-charity-needs-to-consider-using-google-aps/#comment-4191</guid>
		<description>[...] I&#8217;ve said this before and I&#8217;ll say it again: Microsoft Office doesnâ€™t just cost you $139 per user, it also costs you in money and man-hours required to manage keeping the various products up-to-date, secured, and backed-up on computer hardware that often requires additional disk and/or RAM with each iteration of Office and/or the Windows operating system. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve said this before and I&#8217;ll say it again: Microsoft Office doesnâ€™t just cost you $139 per user, it also costs you in money and man-hours required to manage keeping the various products up-to-date, secured, and backed-up on computer hardware that often requires additional disk and/or RAM with each iteration of Office and/or the Windows operating system. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 5 Things Churches and Charites can learn from Google &#187; Heal Your Church WebSite</title>
		<link>http://healyourchurchwebsite.com/2008/03/05/5-non-technical-reasons-your-church-or-charity-needs-to-consider-using-google-aps/comment-page-1/#comment-4188</link>
		<dc:creator>5 Things Churches and Charites can learn from Google &#187; Heal Your Church WebSite</dc:creator>
		<pubDate>Fri, 10 Oct 2008 14:11:25 +0000</pubDate>
		<guid isPermaLink="false">http://healyourchurchwebsite.com/2008/03/05/5-non-technical-reasons-your-church-or-charity-needs-to-consider-using-google-aps/#comment-4188</guid>
		<description>[...] I&#8217;ve said this before and I&#8217;ll say it again: Microsoft Office doesnâ€™t just cost you $139 per user, it also costs you in money and man-hours required to manage keeping the various products up-to-date, secured, and backed-up on computer hardware that often requires additional disk and/or RAM with each iteration of Office and/or the Windows operating system. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve said this before and I&#8217;ll say it again: Microsoft Office doesnâ€™t just cost you $139 per user, it also costs you in money and man-hours required to manage keeping the various products up-to-date, secured, and backed-up on computer hardware that often requires additional disk and/or RAM with each iteration of Office and/or the Windows operating system. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

