Which first, ChMS or Website CMS?

20 07 2011

Christ Church Nashville is in need of replacing both our ChMS (Church Management Software Solution) and our website CMS (Content Management Solution). We only have the time energy and resources to move forward with one solution currently. So which do we chose? Or do we wait until we can do them both at the same time?
The current thought amoung those who ultimately will make the decision is that our website is what lets people know who we are and what we are about so it should be focused on first as a simple and informational site. But can we really place a site up that has little or no functionality, even temporarily? Should we plug in all the tools we are currently using, and then back track add the functionality we will gain by going with a different ChMS?

Our goal is to implement a solution that is as holistic as possible. We don’t want every department to have a different software solution if we can avoid it. Realizing that a single solution cannot do all things well, we would like to see a solution that does as many things as possible well.

For starters, lets look at what we currently have and why it isn’t working for us.

ChMS

Shelby v5
We moved from ACS to Shelby in August of 2001. Overall, Shelby has been a stable and reliable system. The biggest compaints have been that the software is not user friendly and support is not as helpful as we would like to see it be. Also, Shelby lacks tools that are really needed to allow general church staff and volunteers to communicate with the congregation, potential attendees and the world effectively.
Shelby v5 also lacks the inherent ability to utilize it remotely. We have decided that a browser / web based solution is top priority.
Another thing to note about Shelby is that I have been the full time IT person here at Christ Church for almost 7 years now (was a consultant for their IT for 3 or more years prior to that), and still do not know a single person at Shelby personally or by name.

Website

Dreamhost
My belief is that Christ Church Nashville’s website is a ministry for members and non-members, churched and unchurched people. It must be able to clearly and effectively communicate with all people and social media is currently the best vehicle to spread the good news.
Our website is currently hosted by DreamHost at a very low cost to us (a little more than $20 per month). The site was created and maintained by a person who is no longer employed here at Christ Church and the maintenance and upkeep of the site was passed on to me a couple of years ago. Graphic design has been mostly handled by interns who were skilled in that area.
Our hosting plan is unlimited in storage and data transfer and has many tools and plugins available to us. Among other things, we utilize an option provided by Dreamhost to serve our online bookstore sales. I have played around with the CMS options available at no extra cost thru Dreamhost. Those being Joomla and Drupal. Also, WordPress type websites are an option thru Dreamhost. It is my belief that these solutions would be a fit for us but would require more of a time investment than I have to give. Still, this may be the best route to take if we had a reliable volunteer that is knowledgeable in those areas that could implement them.

My opinion is that the web site should be designed around the framework that the ChMS provides, and not the other way around. (Online giving and contributions, small group finder, prayer requests, registrations, volunteer opportunities, calendars, newsletters, etc.) The parable that comes to mind is buying a bunch of watermelons to sell and not having a truck to carry them. Yes, they look great but you can’t get them where they need to go. They are going to ruin.

Build a new site that has no functionality and you will lose peoples interest. Once you build in the new improved functionality, they may tend to already be bored with our site and not come back.

This post is getting long, so I will create another post to continue the journey.

Let’s look at what solutions we need and what we would like them to do. Specifically, how do they fit our mission and goals.