I don't know how many times I've now been contacted about building custom Church websites for various parishes, organizations, and ministries... and most of the time I am unable to accept these requests. I think our Church is finally at the point where the greatest hurdle is not necessarily pastors/leaders misunderstanding the importance of a good web presence, but the lack of great tools for building that presence.
I've seen site-building services such as www.eCatholicChurches.com, www.CatholicChurchWebsites.com, and www.ChurchAddress.com, but
have a few problems with them (note: please read through the comments below this post for some good discussion about the issues at hand):
- The expense of running a website through one of these services — it often costs $30-80/month! A lot of parishes simply can't devote $500-1000/year to a website.
- The need... still... for a parish 'webmaster' (someone to update the content).
- The lack of any kind of recognition by the Church;
I can't even tell if there are any Catholics affiliated with these organizations.(Again, see responses below). Do they truly have what's best for the Church in mind, or are these sites simply trying to make as many dollars as they can and taking parishes for a ride?
- The sites often are very 'cookie-cutter-esque,' and are not very well made for searchability, accessibility, and usability.
Granted, many parish websites are horribly bad when they are set up for free by some self-assigned parish 'webmaster' (I really dislike that term; seems so early-90s!), and the aforementioned services are leaps and bounds better than the ugly animated-GIF-infested parish pages. But I think we can do better.
Parishes as Communities of Faith
If parishes are truly supposed to be devoted and faithful communities in real life, why can't we turn that community-mindedness over to parish websites as well? And can't we find a way to help parishes—many with little to no budget for a website—have some sort of parish community site?
Essential features would be:
- A calendar of events; anyone can add an event, and the event can be approved by whomever the parish designates with that authority.
- Organization/Ministry pages; able to be updated (news stories, calendar items) by whomever is in that parish organization or ministry.
- Pastor's Blog (and associates, if need be); able to be easily updated by the Pastor, and with podcast capabilities if he so chooses. Comments can be on or off. RSS feeds are a must.
- An informational page, with Mass times, contact info, and other Sacrament times (ideally, this page would also automatically generate an XML or JSON file which sites like FlockNote and MassTimes could use to automatically update their databases.
- Easily buildable online forms - for registration, baptism, etc.
- Donation systems (or an integrated donation system for Archdioceses) — able to use PayPal, eAuthorize, or some other standard and trusted system.
- Photo Galleries – parishioners might be able to upload their own photos from parish and school events to share with others.
- (Possibly:) A way to integrate a school website... although school websites are a whole different beast, in many ways.
To set up one website like this, using Drupal, would take a few hours at least, and then a few more for a custom theme. However, if we were to make a Drupal installation profile (like the Open Atrium project does), we could have a quick and easy site setup for multiple parishes, and the only concern would be hosting and bandwidth... which I would hope (Arch)Dioceses, and possibly also bishop's conferences, could help pay for.
Open Atrium is a project management system / Intranet powered by Drupal and is very easy to set up using an installation profile.
With Drupal, we could maybe set up one server/VPS for each (Arch)Diocese, and have a Drupal multisite installation, with a site for each parish (if nothing else, you could set up something like parish-name.archdiocese.com for each parish).
Any takers? If not, I will keep this on my back-burner for a while until I get more time to work on it ;-)