I’ve been away a lot since the end of April: first to Washington, DC, Virginia, and North Carolina; and subsequently to the state of Washington. Now that I’m back, I find that I’ve more or less agreed to take over my church’s web site, which has needed to be updated for quite a while. My predecessor did a nice job of setting it up, but as so often happens, these things are difficult to maintain, particularly as his interests and life circumstances shifted. Anyway, this seems to be an area where I can be of help, so I’ll do the best I can.
My first thought was that I’d have to transfer the church domain. But it turns out that no one is particularly wedded to the existing one — “northucc.org” — and anyway everyone calls the place “North Church.” Neither “northchurch.org” nor “north-church.org” is available (a certain famous church in Boston owns one of them), but plenty of similar ones are. I’ve sent a list of possibilities to the pastor. The main thing is to find a domain name that we like and that is more or less intuitively obvious to anyone looking for North Congregational United Church of Christ in Columbus, Ohio.
Once a domain name is registered (which takes only minutes), my initial thought was to build the site around two platforms: a web site per se (similar to what has already been done — I’ve downloaded the existing files and can use them as a basis); and a WordPress blog similar to Radical Civility. With a WordPress blog it is possible to have one person with permissions to administer the blog — that is, universally edit everything in it, modify defaults, etc. — but give others permission to upload entries and so make it a group blog. For example, the pastor could upload his sermons as entries. Other members could provide updates regarding various church activities.
My impression is that blogs often attract more traffic than static web sites, so I think it makes sense to make the blog the church’s “public face” insofar as possible. That’s not the usual practice at the moment for church sites, but I suspect it will become so as the dynamic becomes more apparent. Certainly plenty of ministers already have blogs as adjuncts to their church web sites; I’m just proposing to reverse the emphasis. That’s not a decision that needs to be made formally. We can just create both the web site and blog and see what develops.
The church’s monthly newsletter, The Northwind, is another resource that really needs to be made available online. Doing so would give visitors a very good idea of what the congregation is like, what it does, etc.
The website falls under the jurisdiction of the Evangelism Committee, so I’ve arranged to address them at their the next meeting. Two points need emphasis: 1) how to use the site as a tool for outreach; and 2) the need to develop a cohort of church members with the basic knowledge needed to operate the site. Although one person needs to be responsible for administering it as “webmaster,” it will make it much easier to add and modify content if more than one individual has the ability to do so.
A member of the committee mentioned that she liked the design of another church here in town. I took a look and found that its site is powered by E-Zekiel, which says that it is “committed to providing Christian organizations easy-to-use, powerful, cost-effective, Internet-based communication tools and services. For large and small churches to faith-based non-profits, E-zekiel provides simple solutions to often complex technology.” As E-Zekiel portrays itself, it looks like a good platform for allowing multiple users to add/revise content while maintaining a consistent look, and it has other features that may be useful, too. So it might be just the thing.