Since May, you’ve heard me rant and rave about the end-user this, and compelling content that. I’ve given you several dozen examples of how to manage things from a code-monkey’s perspective.
That said, one aspect I’ve offered scant detail to is the human factors in maintaining a church web site. An issue I was reminded of by the dozens of emails and the triplet of comments generated by Monday’s mention of a content mangement system and church secretaries. Sentiments that I think are best summed up in the following email:
I read your post today about Content Management Systems being used for the church, and I just couldn’t help myself. I had to share all these ideas I’ve been having for the last couple of years. You seem to understand both the technical and practical side of church web sites, so I would love to hear your thoughts…
I am the “lead webservant” for our church, West Park Baptist Church in Knoxville, TN. We started over a year ago doing a redesign of our entire site, www.west-park.org (we still haven’t launched the redesign, so if you go visit, you’ll find plenty of things that need to be healed!). Being a programmer by trade, I had high hopes of finding a content management system that we could use to build our site.
After a lot of looking at the Open Source solutions, we ended up going with (gasp) FrontPage. I know, it’s about as far from Open Source as you can get. And I know, it isn’t really a content management system in the sense that it separates data from display–because it doesn’t. It doesn’t even use real templates. With the exception of the header, footer, and left nav of our web site, HTML is duplicated all over the place.
As a programmer, all those technical insufficiencies just bug me. But it ended up being the best solution for now, because:
- Usability / User Interface
FrontPage’s user interface is pretty intuitive for anyone who knows Word. Our staff does not spend most of their time working with software, but when they do use computers, it’s almost always to use Word. We figured that in the end, our staff could actually maintain a web site done in FrontPage, with a small learning curve.
- 2. Delegation of responsibilities
In our church of 1500, it is not feasible for our 4-person team to keep the entire web site up to date. Our end goal is to have each ministry and small group keep their own portion of the web site up-to-date. With FrontPage, we can delegate the management of those sections to the respective people. I know this can be done with many of the content management systems out there, but at this point we fall back on #1. The more people we have managing portions of the site, the easier our software needs to be. So, FrontPage won again.
- 3. Advanced features of FrontPage Server Extensions (FPSE)
With FrontPage server extensions, everyday users can create web forms that collect data from the user and send it via email to a specified email address. No HTML required…just point, click, and it’s done. FPSE also allow them to do server side includes, syndicate news from MSNBC, and create search forms for their sections of the web site, all from a WYSIWYG interface that they’re familiar with. And because FPSE runs on Apache on Linux, we can find affordable hosting, too.
Even with all this, the fact of the matter is that there is no existing system that does what we want. For example, our church has 30 or more small groups. On the web site, we would like to supply these small groups with online calendars, forums, mailing lists, online studies, that they can maintain themselves. But to do that effectively, we need to tie in to our church management system, Automated Church System (ACS). Otherwise, we end up having to put information into at least two systems independently, and you know how quickly that gets hairy. So, we tried to integrate the web site with ACS. The problem is that it’s proprietary, and we can only export comma-delimited text files, and that gets awfully limited when you’re talking about integrating an interactive web site with it.
As a Christian programmer, I am really longing to see an Open Source answer to this question. Sadly, I think the only way to really get what we need is to build it ourselves. In my opinion, we need to meld the church management system with a web content management system. This approach could open several doors of opportunity:
When a new member joins, entering them into the church management system should automatically create an account for them on the web site. Using that account, they could access online member directories, forums, online giving statements, etc.
When the person joins a small group, the small group leader could login to the web site and assign that person to the small group’s web calendar, forums, etc; and that assignment should filter back to the church management system.
Better yet, when a person wants to sign up for a small group, they should be able to go to our web site, log in, and go to the class they want to sign up for and click “Sign Me Up.” That should trigger the church management system to enroll that person in that small group, and should automatically sign them up for their small group’s forums and mailing lists, etc.
The problem is that I have a vision of what I would like to see, but no time to accomplish it. Do you think there are enough of us Christian programmers out there with enough time on our hands to build a system like this? Do you think there’s a market for this kind of integrated system? Do you think we could make it Open Source? I like the ideals behind Open Source, but I still wrestle somewhat with the economics. Besides that, I’ve never actually been involved in an open source project and would have no idea how to lead one.
Just a whole bunch of ideas and questions that I’d like to hear your take on.
Thanks for taking your time to read this tome. And thanks for your web site. It’s been an enjoyable, informative read ever since I started reading it!
Your Brother In Christ,
I think this is a GREAT set of topics for discussion. I want to hear from you. Comments?