How I decided to drop hyper-fancy content manager systems for a generated static website.
In the end, I got bored of Joomla. It’s not Joomla fault I think, it’s just that keeping everything up-to-date was too time expensive, and in fact my old website got stuck with Joomla 1.5.something.
At a certain point I decided I had to update it. An important premise is that using only rolling-release distributions (Sabayon and Arch) I grow extremely lazy for what concerns manual updates: I am used to have daily / weekly updates done with a single command, and only rarely I have to look to what went wrong. I can accept a bit more effort for upgrading the kernel (namely: a couple more of commands to issue), but I really cannot spend a day for such operation as I was used to when I used Windows - I still remember I was formatting my system every four or five months, now I laugh at myself when it comes to my mind.
Anyway, I searched for instructions for the Joomla update. Updating between minor versions was quite easy: just unpack the patch archive and upload, done. Upgrading between major versions looked a much deeper pain. I also had the idea of seeking which version my favourite package managers propose:
The AUR is fantastic as usual!
Since I have not switched all my systems to Arch - I need a good reason to remove Sabayon, and I have none - I wanted something that was kept up-to-date also in my repository: my idea is that I can keep a local install up to date, and just regularly upload it to the server (and regularly backup it). So I looked around, searching for other CMSs. As everybody does, I evaluated Wordpress, Joomla and Drupal.
Pros: easy, available both in Pacman and Entropy
Cons: considered slow with respect to the others, I would lose my Joomla contents
Pros: I already know how it works, I will not lose my current website content
Cons: I HATE HATE HATE doing upgrades, version 3 not available in Entropy
Pros: require skills (so I will either prove myself valiant or learn more), available both in Pacman and Entropy, fast
Cons: I would lose my Joomla contents
Since I could in the end keep my legacy site in a subdirectory and redirect if needed, I decided to go for Drupal. And this is the result folks: I must admit I am rather satisfied of my choice.
INFORMATION TECHNOLOGY website cms jekyll feeling responsive github git