On Wed, 8 Oct 2025, Dick Steffens wrote:
Thanks. Many to choose from, but it sounds like I'd better stick to
learning WordPress. I've made some progress this afternoon.
What's the audience,
Church website.
At the risk of sounding paranoid and beating the same drum too often,
I would emphasize some points of management:
1. Assume that the church staff or another volunteer will at some
point take over site management, so document EVERYTHING and then
train at least one other person on site basics. Document all
questions raised during the training and their answers. Did I
mention documentation?
2. Make sure the documentation includes any and every customization
you configured into your site, whether it's installing a plugin,
changing variables in some PHP code, adding images or photos, etc.
3. WordPress and its plugins have a long, long history of security
vulnerabilities and exploits. Devise and document a plan for
keeping track of WP security issues and the exact steps necessary
for remediation.
4. Once more: document and train. Document and train. The number of
congregational IT projects setup by well-meaning volunteers that go
orphaned and unmaintained when the volunteer becomes unavailable
exceeds the number of dead Assyrian soldiers left outside Jerusalem
during Hezekiah's reign. If you care for your congregation enough
to get this site up and running, then also take care that it can be
well and lovingly maintained when you are (for whatever reason)
unavailable.
--
Paul Heinlein
[email protected]
45°22'48" N, 122°35'36" W
