Using WordPress After Drupal 7

Like many people I believe, I created websites with Drupal [in my case after Mambo and Joomla] as it appeared attractive for even smaller sites, with sophisticated content management through Views Module and so forth. I started with Drupal 5, moved on to 6, upgraded to 7, and then stopped: Drupal 8 looked too intimidating, with things I barely understood and didn’t feel I needed. Though I later tried an upgrade to Drupal 9, it didn’t go well; didn’t see much that was better, then a minor upgrade broke the site – something to do with Composer, apparently.

Looking around, I learned it’s possible to switch to WordPress; website software I’d earlier dismissed as only for “blogs”, but which had developed a lot, looked more approachable. I indeed made the switch, describing in an article one this site: .

So, how is WordPress after Drupal?

Woah – User Friendliness with WordPress!

First, after I’d very often struggled with Drupal – which evolved even more into software for “developers”, not people with content to show – I found many things are a relative breeze with WordPress. And even the attitudes differ; WordPress instructions etc mostly target regular people, not those fluent in arcane web lore.

For instance, uploading images, even creating simple galleries, is a cinch with WordPress.

Not so with Drupal; indeed, the first time I tried viewing images in a site with Drupal, had to discover why they weren’t appearing: turned out, Drupal by default then stripped out html for images, in what seemed to me an over zealous attempt at ensuring site safety. Later, I tried creating galleries; but a couple of gallery modules weren’t easy to work with – uploading images one at a time was typical, had to put effort in to find how to do multiple uploads. And, those galleries became abandonware, with sparse choices as alternatives.