I'm back in the web design loop, thinking again about how to bring this site back into some sort of action, and have a bit of practical fun messing about with tools in the process. Of course, as I said before, the main reason for having a public site is to present some kind of interesting content, not to play around with software, so I'm doing my sandboxing on a local server this time, and not uploading anything new to the web-hosting site until I've clearly decided what I intend to do. 

I suspect that I'll stick with Joomla in the end, because it actually does what I need, and offers continuity and security. There's no point starting with a radical experimental tool only to have it disappear after a few months. 

One thing I was thinking about was to move from a conventional web CMS to a digital asset management structure, possibly with something like Resource Space. To shift the focus from a public website to a tool for putting stuff into the cloud for my own benefit.  After testing a bit, I don't think this makes much sense. Why set up your own cloud when Apple, Google and the rest offer such cheap out-of the-box solutions? The amount of storage I get from my web hosting company is peanuts compared to what I get for a few euros a month from iCloud. 

Back to CMS, the latest thing I've been testing is the Python-based Plone 5. Looks nice, a lot leaner and meaner than Joomla, but it also looks as though you would have to be put in a lot of creative effort with it to get a site that looks even vaguely professional. I also set up a dummy site with the Typo3 spin-off NEOS last night. That was very impressive, but I managed to break it by uploading a big image. I had it running in a Bitnami stack, so perhaps it wasn't set up quite right: I probably need to have another go there.