About

I began with Drupal using either version 4.6 or 4.7.  At the time the tagline for Drupal was "Community Plumbing" and I was shopping around for a "content management system" that could be used to build one or more online community websites.  My intent was to use online community websites to promote positive social change.

The principle result of this is the V is for Voltage community which focuses on electric vehicles, electric vehicle construction, electric vehicle maintenance, electric vehicle ownership, and so on.

Drupal has a zillion useful features, especially after you install CCK, Views, etc.

What Drupal also has is complexity, and the overhead of maintaining the system from release to release.

A major problem I'm facing is migrating V is for Voltage (and my other sites) from Drupal 6 to Drupal 7.  It's a year and a half after the release of D7, and there are still major chunks of functionality I installed for D6 which are not implemented for D7.  This points to a major flaw in the operation of the Drupal ecosystem - the lack of release-release stability means extra overhead on everyone's part on each major version migration.

The tradition in the Drupal community is that "The Drop is Always Moving" which means that change is constant.  And, indeed, change is a constant attribute of the universe.  What this means in Drupal is that for each major release the core team does what amounts to a complete rewrite of Drupal, and they break compatibility with each module.  This means module maintainers must do major surgery on their modules to keep up, or else be left behind.

I could go on and on .. but what I learned after a couple years of this is that I have more important things to do with my time than fiddle with Drupal.  I have content to write, ideas to promote, etc, and the time I spend on maintaining my sites is a detraction from that core purpose.

This leaves me with the problem of having several existing websites implemented in Drupal.  What do I do with them?

That's what this blog is meant to do, is to document the processes for migrating away from Drupal.

This blog is also an example of the tradeoff between Drupal and other platforms.  This blog is run using the venerable Blogger platform.  It was a few mouse clicks, and the blog is up and running and ready to go.  If this had been implemented with Drupal the setup would have taken much longer, and then I would have had to spend awhile every month or so updating modules, and then sometime in 2013 or so I'd have had to spend many hours puzzling over how to forward port from Drupal 7 to Drupal 8.

The bottom line is that the Drupal community changed between the time I found it and today.  Drupal today is used to host huge enterprise websites, and the community is being controlled by the contractors and consultants who do that work.  The facilities available for Drupal now are excellent, but are geared towards high end websites.  What that means is that an individual who wants to set up a few blogs on their own has been left in the dust.  That's me.  Coughing up dust, looking for an alternative.

No comments:

Post a Comment