2016 - ongoing updates
Development continues this year (although not at the rate of last year) with updates to usability and improved functionality, as well as the usual “Bug Fixing”.
2018 - modules become more flexible
The CMS continued to evolve around the modular structure introduced in the 2015 rebuild. New functionality could be added without having to rethink the whole system, making it possible to develop new features more quickly while keeping the existing sites working as expected.
2020 - more automation
As the CMS grew, more of the repetitive work involved in managing a site was automated. Content could be reused, common tasks simplified and administration made easier. The aim was increasingly to make the CMS do the work rather than make the person using it do the work.
2023 - improved security and reliability
Security continued to become a much bigger part of development. Existing code was reviewed and updated, database handling improved and older parts of the system gradually brought up to the standards expected of a modern website. Much of this work isn’t particularly visible to the person using the CMS, but it makes everything underneath it considerably more robust.
2026 - AI becomes commonplace
AI is now becoming a normal part of development. Not just for writing code, but for doing all the jobs that developers traditionally never quite got around to. Security reviews, unit tests, code checking and documentation can be carried out in minutes rather than hours. Things that would previously have gone onto the “I’ll get around to that” list can now actually get done.