Church Planting, Technology & Culture
29 Aug
A team of us are beginning to build an affordable Church based content management sytem. What are important features that a church system wouldt need? (We’re going to call it, Ekklesia Systems. )

Overview:
1. Built based on Web Standards
2. Powered by a Flexible Open Source Structure – Upgrade path.
-Separation of Content and Web Features (modify navigation and website tools without disrupting content.)
-Separation of Content and Presentation (maintain consistency in design for all new content created with style-based content authoring.)
3. Integrates powerful Technologies – (mp3, podcasting, rss)
4. Easy to Use Administration
5. Great Design
Features:
Content Management System
o Editable classification and specific templates to handle:
Sermons
Articles
Teaching/Study Guides
o WYSWIG Editor
o Ability to add elements such as attachments (pdf/doc), images, mp3s, podcasts,
o RSS
o Relevant Linking – Keyword ‘meta data’ to display relevant resources (eg. A sermon on God’s Sovereignty would show books, teachings or other resources attached to this term.)
o Photo gallery
o Resource Web Directory (recommended reading lists, links, etc.)
Contact Management System
o Newsletter tool
Event Management System
o Web-based Calendar
o Events (Sunday, home groups, small groups, etc.)
Membership System
o Personalization and Relevancy- Provide content to visitors based on their segmentation preferences and interests. Content can be linked by relevancy to create a rich user experience.
o Membership Features – Offer exclusive content, web features and secure login areas to create and modify profiles for members.
o Online Members Directory
Assimilation System
o Track guests through the assimilation process towards membership.
Interactive System
o Forums
o Custom Applications and Forms
o Blogs
o Classifieds
Tracking System
o Online Visitor Reports
Keep your eye out for Ekklesia Church Content Management System.

Drew is an elder/pastor at Kaleo Church and CEO of Monk Development. Kaleo is a church planting movement in San Diego. Drew spends much of his time thinking about church planting strategy, web missiology and being a husband and father of two (Gideon & Roman). More about Drew Goodmanson.
6 Responses for "Church Website Content Management Systems"
Not reinventing the wheel is the number one mistake I see in the current market for these types of projects — robust open source web application development platforms like xaraya and drupal are rising up as the next generation of Content Management Systems – this is the place where all businesses (churches included) should be headed.
We’ve got to take seriously the advantages of the open source development model in it’s ability to deliver features and functionality that no full time team of 100+ can — and do it much more rapidly.
I’ve consulted on too many project where we’ve made the mistake of using a custom solution built by a 1-5 man shop (some of which I’ve sold to clients) — when they can’t support the required feature set (which is ever geometrically expanding in the current business environment) or they go out of business — then the project is left high and dry.
Sadly — I’ve seen the cycle unnecessarily repeat itself time and time again — as we pick another small shop and begin painting ourselves into the same corner suing a different color.
With the current availability of solid and scalable open source systems to build on, we shouldn’t be making this mistake anymore.
>>
suing a different color
>>
er, I mean using a different color (it sounds so much better without typos)
Thanks Zug. Hey, check out this article:
Just adding some food for thought. (whatever that means)
>>
Writing your own CMS can lead to a solution that is better suited to your requirements, better addresses the needs of your users, and is better understood by your development team. If you have the time and expertise to write your own in-house system, it may well prove the better option.
>>
Nope — I’ve done it a few times — in PHP and ASP — MySQL and SQL Server.
The problem is that this approach doesn’t scale — there is absolutely no way a small shop can stay on top of the feature sets that are being commoditized (and therefore expected by even non-technical clients) via open source web app systems like xaraya, drupal, and the like — or even blogging tools like WordPress, Moveable Type, Blogger, MSN and the like.
Much wiser to build the custom enhanced feature sets for your audience inside the framework of an established extensible scalable system.
More food for thought:
Content Management
The Perfect Publsihing + Community Tool
Sounds like you have most of the needs covered. I know that my church could have used this a while back when designing a new site, I had some input and presented some ideas and samples but eventually they paid someone to create something that is barely more than a few static pages. I am continually shocked at the number of churches that are still missing the boat in regards to web ministry.
Leave a reply