<?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: Church Management Theory</title>
	<atom:link href="http://joshua.remote-app.com/2008/10/05/church-management-theory/feed/" rel="self" type="application/rss+xml" />
	<link>http://joshua.remote-app.com/2008/10/05/church-management-theory/</link>
	<description>My blog of programming, hobbies, and thoughts.</description>
	<lastBuildDate>Sun, 27 Dec 2009 20:49:36 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joshua Rountree</title>
		<link>http://joshua.remote-app.com/2008/10/05/church-management-theory/comment-page-1/#comment-58</link>
		<dc:creator>Joshua Rountree</dc:creator>
		<pubDate>Mon, 06 Oct 2008 07:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.mycfblog.com/index.cfm/2008/10/5/Church-Management-Theory#comment-58</guid>
		<description>The community front-end would be a predefined website that you can customize 100% all the way down to CSS/HTML like a content management system template.

External data that will be accessible will include and is not limited to:
Person information(secure), Calendar Detail/Events, Group information, Content Management(for giving your staff an easy to use interface to manage their website content), and more.  This list isn&#039;t set in stone and the amount of detail is lack.  As we get the administrative side rock solid we will then begin our development on some of the other aspects such as iPhone interface, API, User Front-end, etc.

We hope this helps!</description>
		<content:encoded><![CDATA[<p>The community front-end would be a predefined website that you can customize 100% all the way down to CSS/HTML like a content management system template.</p>
<p>External data that will be accessible will include and is not limited to:<br />
Person information(secure), Calendar Detail/Events, Group information, Content Management(for giving your staff an easy to use interface to manage their website content), and more.  This list isn&#8217;t set in stone and the amount of detail is lack.  As we get the administrative side rock solid we will then begin our development on some of the other aspects such as iPhone interface, API, User Front-end, etc.</p>
<p>We hope this helps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SoulEmbraced</title>
		<link>http://joshua.remote-app.com/2008/10/05/church-management-theory/comment-page-1/#comment-57</link>
		<dc:creator>SoulEmbraced</dc:creator>
		<pubDate>Mon, 06 Oct 2008 07:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.mycfblog.com/index.cfm/2008/10/5/Church-Management-Theory#comment-57</guid>
		<description>Interesting. I&#039;ve turned on my church leaders onto this, and I&#039;ll forward them this post to see if they can provide you any input comparing Chrrch to other mgmt systems they may have use. What would the &quot;community front-end&quot; entail?  Also, what external data would be accessible from your system?
Thanks.
Andy</description>
		<content:encoded><![CDATA[<p>Interesting. I&#8217;ve turned on my church leaders onto this, and I&#8217;ll forward them this post to see if they can provide you any input comparing Chrrch to other mgmt systems they may have use. What would the &quot;community front-end&quot; entail?  Also, what external data would be accessible from your system?<br />
Thanks.<br />
Andy</p>
]]></content:encoded>
	</item>
</channel>
</rss>
