Yesterday, I deleted my WordPress installation at Spooklit and moved the Grav installation I've been working with to public_html. I'm quite happy with it! Although, given Spooklit's content, it took me a while to settle on a structure for posts/categories/pages. I considered giving b2evolution (the CMS I used at my very first domain, back in the early 2000s) a whirl, because of the way it handles multiple blogs; but I'm enjoying Grav so much that I just went with a simple, single blog structure, with an eye toward complicating the whole thing later when 1. Spooklit has more content, and 2. I better understand how to get Grav's Taxonomy List and SimpleSearch plugins to work with what are, essentially, multiple bogs on one site.
But another thing happened a couple of days ago (even if I only became aware of it yesterday): ExpressionEngine became free and open source. I remember a particular designer friend going on about how great ExpressionEngine was back when I was struggling with the notion of moving from TypePad to WordPress (.org) and still doing design work with a rollerball pen. I couldn't afford ExpressionEngine at the time, but Dave's argument was so convincing that, given that I now have both the time and server space to do so, there's no universe where I'm not installing ExpressionEngine in a subfolder, at least to play with it for a bit.
I find the timing of ExpressionEngine's change glaringly appropriate, given what's coming with WordPress 5.0 (read the comments), and WordPress' current dominance of the blog/CMS market. Will open sourcing EllisLab's CMS provide the competition that WordPress needs? Probably not in the short term. But it could certainly help to increase platform diversity, which is always a positive.
As excited as I am to set up an ExpressionEngine playground, I'm hesitant to give up the freedom I'm experiencing from having my (admittedly small) sites flat-filed. I'm actually having to retrain my thought processes to flow along simpler lines, to remind myself that I can just login through Transmit or cPanel and delete whatever file I want gone, instead of having to poke around my CMS' admin in order to delete something from my site and database. It's great having those obstacles to direct action out of my way, and I am loathe to put them back in place.
And the benefits of sacrificing that freedom for a database-driven CMS?
We'll talk about that in a few days.
- If you're hosting at SiteGround—or, I guess, any other host where you've installed WP via Softaculous—uninstalling via Softaculous really is the easiest way to get both WP and its database both good and gone.