Unless you want to spend the money to hire a professional developer, there just doesnâ€™t seem to be a great solution out there for churches. Now, I understand that there are some good efforts going on. My problem with those is that I need to be able to hand off the daily maintenance of the site to a staff member or a ministry volunteer and the â€œgood effortsâ€ are still not very user friendly.
Our church is currently using the Joomla CMS to handle the website. Keep in mind, Iâ€™m a systems administrator, not a web developer. Weâ€™re finding that Joomla may not be as flexible as we need it to be. For one thing, the pastor and elders want a specific look, or â€œtheme,â€ for our site. While I can come close using templates downloaded from the web, we canâ€™t quite get there. Iâ€™m sure that a developer could jump in and make the thing look beautiful, but I struggle with paying that kind of money out.
While I like the all-in-one integration of Joomla, Iâ€™ve been kicking around the idea of splitting the functionality of our site into multiple systems. I think weâ€™d still use Joomla for the main site. Then for blogging and pod-casting, I might use Word Press. For online bible study, Iâ€™m considering Moodle. The problem with this is the need for multiple user account databases, which increases management overhead and end-user frustration.
The best solution would be to have a full time technical person on staff at the church. That sort of commitment would allow focus on the site and the time and ability to learn the system. Weâ€™re not quite big enough to tackle that yet, though.
Iâ€™ll keep you posted with my progress on this little (huge) project.
I’ve been in IT for over 25 years.Â As a result, I drink way too much coffee, my eye occasionally twitches, and no I will not fix your computer.Â I’m also a photographer, videographer, and an elder at my church.
Did I mention I like coffee?