...
If we have to offer the users of the secondary CMS content support (a probably scenario), then we could 'pull' this back from Catalyst and do it in-house. However, it seems foolish to try to host and support the CMS in-house, as we are trying to out-source these services for Squiz.Maybe we need to consider 'hosting' ourselves (knowing the limitations), as we at least can start moving sites of various (old) platforms onto one alternative. Maybe we have online documentation for users as a 'level 1', we internally offer level 2 and then use a vendor for level 3.
What, if anything, can we do this year, and port/forward to a future next year that has yet to be funded?
There may not be anything worth doing now with little certainty on future funding. Even if we knew we had a much less than required budget, I am unsure on the wisdom or value of moving forward this year.
Jane and Paul were unable to identify any sites that had sufficient on-going funding to risk building something this year without knowing what would happen next year.