Trigger Warning for gentle satire.
Picture the scene. You’re there at church, and some bright spark turns around and suggests that you should have a church website. Instead of rejecting the idea completely, here are ten reasons why you should say no:
1. Someone would need to build it.
2. Why would people go to a church website, when they can just come to a Sunday Service?
3. Someone would need to update it.
4. We can’t ask the obvious people who always say yes to things to do another job!
5. We’ll need to arrange a committee to decide how it will look!
6. Don’t we need photos for something like that?
7. We’ll need to decide why we need a website.
8. We have a Facebook group, why do we need anything else?
9. Faith comes by hearing. In person. On a Sunday morning. Not via a MP3 recording!
10. Having a website may upset the person who puts together the church notice sheet.
Any more reasons to say no?
Blogger / WordPress / Email List Guy.
Support worker. Short sentences. I write Bio in.