CMS Options. An Exploration in Future Development Choices


So I mentioned in my last post about getting a few CMS's together and working on drilling down on seeing how they work and getting into developing for them. I'm happy with my list at this point and think that I'll be looking at the following systems in the following order:

  • Grav - As far as flat-file CMS's go, it was out of Grav or Bolt. Bolt seems nice so given they both use Twig for templating it's highly likely I may look into Bolt at some point in the future as well. I just liked the look of Grav and I'm pretty sure I found it before Bolt so it had the running lead and became first pick.
  • ForkCMS - For something to move into a CMS that isn't Wordpress (which I've excluded from this list because I've got a fairly good idea already for styling and developing for it) I've chosen Fork. It seems like it's straight forward for non-developers to use, which is an important consideration when working with people who just want to be able to build pages or post news without having to jump through hoops or complex interfaces. Some other options here were Concrete5 or ModX. I'd used ModX once before and didn't like it that much at the time, that was quite a few years ago now so it's probably changed a fair bit (or at least my perception on things probably will have). Concrete5 is another option I'd probably look at down the line similar to Bolt/Grav.
  • Typo3 - I'd be a long way off learning this one, but for enterprise-level solutions Typo3 seems like a powerful option. It looks complicated from an administrative standpoint though so I'm guessing this would be more of a personal exploration project, at least initially, before I consider doing anything with it.

So I've got Grav for small-scale websites, ones that may be updated occasionally with new content and pages but not so heavily to require a database or complex ACP. Fork for medium-scale, where a database for managing pages, posts and media would be useful for site admins, but not overly complicated in terms of functionality and permissions to actually use the site. And Typo3 for eventual large-scale projects, the kind that would probably need more than one developer to be honest, which is why it's so far down my list on things to learn.

The advantage is that they all use Twig, so learning that will at least be a transferable skill to the others - short of system-specific elements - to cut down a bit on adapting to the new system.

I'm starting with Grav as I'm looking at using that for my new website. Like I said, Wordpress hasn't been the greatest choice for something so basic. A combination of Grav and this blog should be more than suitable to do everything I need. I thought about starting with Fork, but from a usability standpoint it's very similar to the new system we're going to be using at work so I've got no dramas leaving that for a bit so I don't confuse myself between the two.

In the interim I'm in the market for some new screens so I'm looking at ones that will be good for developing with. I was going to go 1440p so I could get high refresh rates for gaming, but I'm increasingly realising that I do more development than gaming so I'm prepared to sacrifice refresh rate and bump up to 4K for more screen real estate. More on that another time though.

That's all for now, see you in the next one, Scott.