Church Management Theory
Throughout the time we have researched all the church management systems available out there. Some purely software based and some are web applications hosted as a service.
Some of them are in a different paradigm such as community based where all of the administrative tasks are done in the same environment as the congregation experience.
We do not necessarily feel that combining the 2 should be done. This creates a user experience geared for untrained users which creates a poor administrative user experience.
Our goal with Chrrch is to start by creating a supurb and easy to use interface for administration of a church and then build a community front end that is designed with limited capabilities for the congregation to use and not mix logic amongst the two.
We also plan to build extensive APIs for external websites to feed data from our system with a special developer key that is assigned to the domain.
Let us know your thoughts!
-jr
2 Replies to "Church Management Theory"
Joshua Rountree on October 6, 2008
The community front-end would be a predefined website that you can customize 100% all the way down to CSS/HTML like a content management system template.
External data that will be accessible will include and is not limited to:
Person information(secure), Calendar Detail/Events, Group information, Content Management(for giving your staff an easy to use interface to manage their website content), and more. This list isn’t set in stone and the amount of detail is lack. As we get the administrative side rock solid we will then begin our development on some of the other aspects such as iPhone interface, API, User Front-end, etc.
We hope this helps!
SoulEmbraced on October 6, 2008
Interesting. I’ve turned on my church leaders onto this, and I’ll forward them this post to see if they can provide you any input comparing Chrrch to other mgmt systems they may have use. What would the "community front-end" entail? Also, what external data would be accessible from your system?
Thanks.
Andy