I have decided that hacking around with a content management system I don’t really like is not productive and am therefore going to bite the bullet and ditch Drupal.
Drupal has powered this site for over a year. I started using it primarily on the advice of Sam Sharpe who, amongst others, had been responsible for installing it to drive the Imperial College Union web site.
The trouble is that Drupal is too much of a messy mixture of things that work okay but not really well.
I am going to switch this site to WordPress just as soon as I can. I have selected WordPress partly on personal advice from Suhaib Fahmy and Mike Moate and partly based on my own research. I think Tom Markiewicz’s commentary sums it up rather nicely.
As far as Imperial College Union is concerned I think there are no firm plans as yet but it is accepted that Drupal is not really viable for a multi-user, ‘corporate’ system. Plone looked interesting but it would be a fair amount of work to implement and the Union has yet to find a ‘volunteer’ to do the work.
Drupal was an acceptable solution at the time.
To be fair, I installed Drupal for ICU because it was the best thing out there at the time, but to be honest, it’s overkill even for them. There’s too many features that just aren’t necessary for the Union site – I think they’d be better employing a consultant to design or implement a good system.
And to be honest, I use WordPress for my blog.
Non lasciare perdere..
http://www.urduword.com/cgi-bin_dictionary/standard_search.cgi?Cobrand=&Output=Print&English=Mustafa
Drupal underpowered, not over, for ICU
Sam, it’s unfair to suggest that Drupal is overpowered for Imperial College Union. In my view it was underpowered. I don’t really want to get into a detailed discussion but it couldn’t even provide a sensible system for setting different levels of page editing permissions for different parts of the site to users/groups. That’s why we started looking at migrating to Plone.