<?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"
	>
<channel>
	<title>Comments on: Making a church website sub-blog: 1. starting up</title>
	<atom:link href="http://boyinthebands.com/archives/making-a-church-website-sub-blog-1-starting-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://boyinthebands.com/archives/making-a-church-website-sub-blog-1-starting-up/</link>
	<description>Scott Wells on the practice of Christian faith</description>
	<pubDate>Sat, 05 Jul 2008 23:42:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Boy in the bands &#187; Blog Archive &#187; Making a church website sub-blog: 2. cleaning some features off</title>
		<link>http://boyinthebands.com/archives/making-a-church-website-sub-blog-1-starting-up/#comment-25378</link>
		<dc:creator>Boy in the bands &#187; Blog Archive &#187; Making a church website sub-blog: 2. cleaning some features off</dc:creator>
		<pubDate>Sat, 05 Aug 2006 14:44:20 +0000</pubDate>
		<guid isPermaLink="false">http://boyinthebands.com/archives/making-a-church-website-sub-blog-1-starting-up/#comment-25378</guid>
		<description>[...] To read part one in this series, click here. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] To read part one in this series, click here. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Wells</title>
		<link>http://boyinthebands.com/archives/making-a-church-website-sub-blog-1-starting-up/#comment-25340</link>
		<dc:creator>Scott Wells</dc:creator>
		<pubDate>Sat, 29 Jul 2006 20:00:20 +0000</pubDate>
		<guid isPermaLink="false">http://boyinthebands.com/archives/making-a-church-website-sub-blog-1-starting-up/#comment-25340</guid>
		<description>1. The static pages are quite easy with WordPress. See my "About Scott Wells" page off of the main blog page.

2. You're right, of course, and more than that there's little need for a score of little churches having their own host, or even their own domain. Might be a good shared project for a UCC association or UUA district. Or twenty-first century version of a missionary publishing house. The hosting and volunteer set-up support, I mean. I could see a whole bunch of sites initiated at a denominational meeting, for instance.</description>
		<content:encoded><![CDATA[<ol>
<li>
<p>The static pages are quite easy with WordPress. See my &#8220;About Scott Wells&#8221; page off of the main blog page.</p>
</li>
<li>
<p>You&#8217;re right, of course, and more than that there&#8217;s little need for a score of little churches having their own host, or even their own domain. Might be a good shared project for a UCC association or UUA district. Or twenty-first century version of a missionary publishing house. The hosting and volunteer set-up support, I mean. I could see a whole bunch of sites initiated at a denominational meeting, for instance.</p>
</li>
</ol>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michelle Murrain</title>
		<link>http://boyinthebands.com/archives/making-a-church-website-sub-blog-1-starting-up/#comment-25339</link>
		<dc:creator>Michelle Murrain</dc:creator>
		<pubDate>Sat, 29 Jul 2006 19:43:01 +0000</pubDate>
		<guid isPermaLink="false">http://boyinthebands.com/archives/making-a-church-website-sub-blog-1-starting-up/#comment-25339</guid>
		<description>Hi Scott,

I agree with you that this is a huge step up from a lot of church webistes. There are two issues, though. One, is that most churches need about 5 static pages (about, history, services, yadda) - and blog-centric CMSs have a hard time incorporating that pretty simple need. 

Second, I've worked with a number of churches, and, well, I think it's assuming a lot that many have enough expertise on hand to do those easy steps that you've outlined above. Yeah, they are easy for you and me, but... It's surprising to me, but one of the things I've learned is that things like dealing with domain names and hosting are some of the most difficult things for people who are even moderately tech savvy to do. 

Anyway, it's certainly a good contribution!</description>
		<content:encoded><![CDATA[<p>Hi Scott,</p>
<p>I agree with you that this is a huge step up from a lot of church webistes. There are two issues, though. One, is that most churches need about 5 static pages (about, history, services, yadda) - and blog-centric CMSs have a hard time incorporating that pretty simple need. </p>
<p>Second, I&#8217;ve worked with a number of churches, and, well, I think it&#8217;s assuming a lot that many have enough expertise on hand to do those easy steps that you&#8217;ve outlined above. Yeah, they are easy for you and me, but&#8230; It&#8217;s surprising to me, but one of the things I&#8217;ve learned is that things like dealing with domain names and hosting are some of the most difficult things for people who are even moderately tech savvy to do. </p>
<p>Anyway, it&#8217;s certainly a good contribution!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
