GoodGNUs

Back from giving my new “Free Software in the UK Voluntary Sector, and why you should care” talk to Manchester Free Software Group. A small audience, but a nice rambling debate over many fields, and good real ale at the Lass, so all-in-all a good evening.

Before travelling up to Manchester I spent a day not listening to Election news (okay, mostly not listening - I tuned in to the Daily Politics Election Debate), and working on websites - always a nice break from pure SysAdmin work. One WordPress site, and three Drupal sites. Not necessarily a good idea.

Drupal is, admittedly, far more complicated than WordPress, but has a lovely modular construction, and is easy to theme and style, so working on just one WP site (out of a total of 4 websites) actually doubled my workload, as I struggled to find ways of doing things on the (admittedly) easier platform.

Counter-intuitive

Why was I doing 3 Drupal and 1 WordPress site? Good question. The three Drupal sites are voluntary efforts for local voluntary groups: they could grow and scale in unpredictable ways, and Drupal offers the simplest way to start, and to grow, without holding you back if your needs suddenly become somewhat complex. Despite its higher price-of-entry (even the text-editing interface for the end user needs to be added manually, never mind the work of adding a custom content type to replace the lamentable standard calendaring), Drupal installations are easily repeatable, easily customisable, and so flexible that grown SysAdmins often weep with the simple joy of it all.

WordPress, on the other hand, works better out-of-the-box, particularly for the end user(s) who will be maintaining content on the site, and so is the obvious choice for low-cost sales to clients wanting rudimentary content management. Obvious choice? Well, obvious doesn’t always mean right. In this case Drupal, the counter-intuitive choice, would have been more efficient - even had I charged my WordPress rate for it (which is half the price of my cheapest Drupal rate), for I’d have got the job done more quickly alongside the other Drupal sites, without thinking my way round WP theming and which modules got around the limitations of the originally-blog-based design.

The lesson learned? Love your tools for the job they do, but charge for the end results, not the use of the tools - less pain all round, however wrong it seems. Tomorrow, more web: Quick, someone book a place on one of my courses before I’m seduced to become purely a web developer ;-)

LinuxUser & Developer, issue 86, just came through the letterbox. I flicked through and a reader’s letter caught my eye - not because it called my Arduino article “wonderful” <blush>, but for its links to CopyLeft hardware resources.

Small Form Factor, Free Software, Open Hardware - 3 out of 3 for the NanoNote.

QI-hardware, producers of the Ben NanoNote, and the MilkyMist One boards are all projects deserving much wider publicity within (and beyond) the Free Software and hardware hacking communities. I’m certainly very tempted by the NanoNote.

Thanks to Wolfgang Spraul of QI Hardware for writing in to LU&D with the links.

Picture Credit: http://sharism.cc/ - licensed under CC-BY-SA 3.0.