The previous post, which I posted on February 20th, was about the possible extinction of the human race as a result of global warming. Since then, the Covid-19 virus has become a huge threat, and we all have to self-isolate and stay home. It’s not an extinction threat, but it is a threat.
For those of us in paid employment, self-isolation means working from home, which of course brings problems, especially with regards to any children who are in the home. Even though in most cases there will be partners at home who can give the home worker a hand looking after the children, it may well be that both partners are working from home, and it then becomes a question of how child care is arranged between the partners.
That could be a problem of course. But for those of us whose children have left home, there is a different issue. Typically, a married couple or long term partners have different interests. That’s fine in a “normal” (scare quotes) situation, but in these unusual times, couples are forced more closely together.
That can be a mixed blessing. You may be able to recapture some of the attraction that brought you together in the first place, which, while not lost, has mutated into a more mature relationship. But you have matured, and you will have, usually, developed interests which you partner may not share.
They may not share your interests, but they will support you in them. They will tolerate your culinary experimentation, while you will indulge them in their taste for art house cinema.
So, I am a writer and a geek. My wife tolerates these interests, just as I indulge her in her liking for quiz shows on the TV. I actually enjoy them too.
I’m a deep geek. I have written low level routines for several Operating Systems, and I’ve even written programs which run at a hardware level on some. Don’t worry about the terms I use. It just means that I have delved as low as it is possible to do so without actually designing computer chips and the circuits that they operate in.
So, what has this to do with my title? Well, in the absence of doing things like shopping, at the supermarket and other places, which I’m happy to do with my wife in normal times, of course, how do I fill the hours?
Well, I’m spending a little more time on my writing, but on the geek side of things, I’ve been looking at moving my web site from WordPress to Drupal. Not seriously. I’ve long been a fan of Drupal, but I’ve settled on WordPress as my platform of choice, and that is unlikely to change.
Drupal is much more flexible than WordPress. That means of course that it is more complex. WordPress has ‘posts’ and ‘pages’. Pages are static, intended to have a long lifetime. Posts are intended to be ephemeral, at least in terms of relevance. You might want to look at a post from three years ago, but you are more likely to want to read a recent one. Pages are the things that tell people about you (“about” pages) or allow people to contact you (“feedback” pages), and so on.
Drupal has ‘Article’ and ‘Basic page’ ‘content types’ which, roughly correspond to WordPress posts and pages, but you can easily add extra content types in Drupal. Drupal has a highly complex system which allows you to do this, often using one or more of an extensive list of modules which enhance the system.
WordPress also has a system, the plugin system, which allows you to extend the base system. In fact there are thousands of plugins, but if you can’t find one that you want, you may be able to cobble something together from existing plugins.
So these are the things that I have come across so far in my geeky delving. I downloaded the Drupal 8 package onto my ‘server’ (otherwise known as the computer in the back room) and installed it.
Drupal works out of the box, after a fashion, but you would probably not use it like that. Some things can be fixed, like the site logo, but others need one or more modules.
I set about downloading and installing the modules necessary to make the site look better. One example of Drupal’s quirkiness out of the box is that Articles and Basic Pages have addresses like https://<site-name>/node/293. A module is necessary to change it to something user friendly like https://<site-name>/feedback for the feedback form.
Somewhere along the line I discovered that the correct way to install Drupal and its modules these days is to use a program called ‘composer’. This is basically a package management system. Yes, yet another package management system to learn. Oh well. So I blew everything away and started again from scratch.
Next I downloaded the modules necessary to allow me to import my WordPress website into Drupal (using ‘composer’). I always knew that it wouldn’t be an exact fit, but at least I would be able to see what it looked like, and what I had to do to make it look reasonable. I wasn’t trying for an exact copy of my WordPress site.
That was a lot better, but I wanted to tweak the styles a little, so I sub-themed it and created a small file with just my changes in it. This small file overrode the parts of the main theme, while the main theme supplied the rest. Or so the theory goes. In fact I had to add some parts of the theme configuration (the ‘regions’) to my sub-theme to make it work properly. I don’t know why sub-themes don’t inherit everything from the main theme automatically. It seems sort of broken.
I discovered that the images in my Drupal site still pointed to my WordPress site, which was a nuisance. One way to prevent that would be to edit the Import file and manually change the addresses. Definitely do-able, but I shelved that problem for now.
Another thing that I spotted about images was that the images that I uploaded appeared under the ‘Images’ tab of ‘Content’ part of the Admin pages. But there was another tab, labelled ‘Media’ which was empty. After a bit of reading I discovered that there is move away from images towards Media Image objects, which are more like WordPress Media images.
Which sounded great until I found that there Media Image objects could not (currently) be embedded into content via the WYSIWYG editor. No button. But this is, fortunately, scheduled to appear in the next release of Drupal.
And that’s about when I gave up. Drupal is a great CMS, but it is not easy to learn, like WordPress. I could use it, but it would take a lot of work, and maybe I’ll delve into it again at some time, but for now I’m happy with WordPress.
Drupal is flexible, but the price of that flexibility is complexity. I was trying think of an analogy to contrast the two CMSes, but the only ones that I could think of denigrated one or the other in some way. There’s more than enough room for both.