Hi

I'm helping to run a site for a Church with an excellent history, and I've recently been asked to produce a community-update-able resource for the church's various monuments and historic artefacts. The basis for the content will be a survey undertaken by NADFA (http://www.nadfas.org.uk/) and should contain both images and formatted text. The hosting will be a Linux shared-hosting solution with all of the usual perks and restrictions (e.g. PHP, MySQL, no shell access, etc.), and I think will be distinct from the main site in both integration and appearance, though some customisation would be preferred.

So far these requirements can be any by any number of software solutions, but the one I'm struggling with is appropriate validation of updates. The requirement put to me was that the public should be able to submit content, but that this content should be screened before it is made available on the site. The founding philosophy of most wiki software appears to low restriction, concentration on reverting to earlier article versions rather than screening - this isn't a favoured approach for the church.

I'm struggling to come up options. I've experimented with a couple of wikis, but struggled to make progress.

Is there a good solution to my problem? What are the alternatives / best compromises?

Any help appreciated. Thanks

Stuart