Scott Reese on Myspace & Paul

In case you didn’t see Scott Reese’s post on Myspace & Paul, I wanted to highlight it even though it’s been four weeks since he posted it. Scott is doing some very solid thinking here.

Since summer of 2005 I’ve been thinking a great deal about how blogging and social networking sites (like Myspace, Xanga, and Facebook) can be used for evangelism and outreach. See some of my previous posts on the subject here, here, here, and here.

I’ve made some efforts to educate management here at Resurrection about the potential, but haven’t been able to spark them into action yet. Is anyone out there aware of a church that’s effectively reaching out through social networking sites?

Online community is more than forums

Mark Stephenson, director of Web Empowered Church (WEC), posts here about how “online community” used to mean forums, but now takes many different forms. These days there are many places on a site where users could potentially post their own thoughts, requests, questions, feedback, and so on. Mark explains how WEC already has a wide variety of extensions for TYPO3 that provide church-specific functionality that fosters online community.

MegaVoice

Lee Grady at Charisma Online posts here about MegaVoice, a company that makes a solid-state, handheld audio player device, similar to an iPod. The MegaVoice is preloaded at the factory with audio that can’t be changed by the user, and is capable of running on solar power. Using these devices, illiterate people all over the world can now hear the Bible read in their native languages. How cool is that?

More background here.

Integrating CRM and the Web

Duncan Rein, CEO of Silas Partners, posts here regarding how CRM (Constituent Relationship Management) should be and inevitably will be fully integrated with the church’s website. This is further fuel for our previous discussion with Tony Dye and others about Church Management Systems (ChMS) and Content Management Systems (CoMS).

To put it in concrete terms, at Resurrection we’re using TYPO3 for content management and Shelby for church management/CRM. I’m in agreement that ultimately we need to: A) integrate the two; or B) replace both with something else already integrated; or C) develop an open source church management/CRM that we can natively integrate with TYPO3. Right now we’re working on option A, but somewhat reluctantly since this is inelegant and it’s difficult to see how well it will work over the long term. Option B isn’t a great one for us because we’re fully committed to TYPO3 and Web Empowered Church. That leaves option C, for which my heart yearns, but we can’t pursue because we have no funding or interest among executive management here.

Hmmm … Maybe we take Tony’s suggestion and sneak this in the back door by gradually building a CRM/ChMS in the form of TYPO3 extensions?