Eighteen months ago I knew virtually nothing about websites, web design or anything else. To me, terms like HTML, CSS, RSS, and the like were all worse than “Greek to me” - at least I sensed some purpose to knowing Greek as a pastor. Techno-jargon seemed far less important.  But after a year of working through website stuff for the church, here is what I’ve learned: Link to BetaChurch Article >>

Yes, another article on church web design.  I’ve been (or have tried to be) quiet on the this topic lately, because I’m not actively engaged in building any church websites so was starting to feel like a “Monday morning quarterback”.

There’s a difference with this article, though, that makes it worth linking to. 

Ben Dubow, the author, isn’t a web developer—he’s the pastor of St. Paul’s Collegiate Church at Storrs in Connnecticut.

Here’s a few of Ben’s “Ten Things to Know About Your Church Website”:

• 1. The web is probably the first place people look for a church—before the yellow pages, newspaper, or anything else.
• 2. Prospective visitors have already formed an idea about your church based on your website - good or bad.
• 3. A website communicates your “true values” to people.

Good stuff.  I’m encouraged to hear these words coming from the Pastor of the church.  I’d love to see Ben’s article get picked up and published in other places where Pastors with less of an “Internet Mindset” will read it.

Christianity Today - are you listening?