Why Wordpress?

I'm planning a training course to help a community association learn how to build and run its own website. And I'm using a hosted Wordpress.com site as the platform for this training, as opposed to other possible solutions, suich as self-hosted Wordpress, Typepad, blogger, drupal, joomla, build your own in dreamweaver, etc. But why Wordpress?

After years if patiently explaining ftp to people who didn't want to know about ftp I'm hoping that choosing a theme and agreeing what pages to have on their site will be more useful, engaging and fruitful to most people than having to work through the back end techie bits or get to grips with html. It seems an ideal way of helping people understand the process from the front end side of things, like what it looks like and what it has on it, with more time to explain some of how it works and play with the CMS-style administration interface.

I run a wordpress-hosted site as ICT Champion, having previously used blogger for some time. I should say that I've also set up a self-hosted WP site and I did it in about an hour but that included 45 minutes finding and configuring an ftp client. Then I spent a lot of time downloading themes and widgets and wotsits and fixes and then uploading them and installing them and remembering passwords and whatever else. Then the latest version was released and I had to carefully back everything up, save everything in then right place and reinstall blah blah

Simple enough stuff to be sure, and offering a great deal of flexibility and control which I may well need at some time in the future, but I can't I can't tell you how much happier I am since I started using a wordpress-hosted site and working within its limitations.

The trickiest techie bits were working out how to have the blog entries appear on a page with a menu tab [by no means intuitive to me but actually just a couple of menu items in different parts of the system] and fruitlessly seeking ways of embedding javascripted stuff like google maps.

Aside from posting I now spend most of my time thinking about categories, which I realise need to drive my navigation much more than the page structure, and re-categorising old stories as I fiddle with my categories. [On which point Blogger has a much easier way of retro-categorising batches of stories than wordpress, which requires you to do one at a time.]

I can also look at promotion and content and editorial issues with a much clearer eye than when I used dreamweaver, when I seemed to spend a lot of time tidying up folders and playing with plugins etc.

By the way I have used Typepad, and I liked it, but it costs, which Wordpress doesn't, so it feels like a safer option for first timers. And I also tried blogger and it doesn't support static pages, so I think it's less interesting to people who want a website, not a blog.

And so I favour Wordpress, both as a nursery slope for people new to building a website, but also because it's probably good enough for most organisation's relatively modest needs.

And in case anyone needs evidence of people's modest needs I leave you with a link to a site which has been used to create a web site/presence by more community organisations than any other in our area - perhaps five times more than we have worked with ten years:
http://www.communigate.co.uk/sussex/viewgroup.phtml?group=3

This is a layer in the internet's geology which is technically outdated but remains a useful reminder of just what people in community organisations want to do on the internet and where they have to start if they're ever going to do it.

More soon on this as I start preparing the notes...