Unobtrusive cms customization with the ability to update to new versions

Question

CMS

There is a cms (version 0.1) that needs to be significantly improved with the possibility of further updating to new versions (0.2, 0.3, etc.).
That is, you need to change the cms code so that you can easily apply your modifications to the new version.
How I see it:
1. Put the sources of version 0.1 into the version control system.
2. Try to write all code changes in separate files and connect them to the cms code as “unobtrusively” as possible (hooks, modules, plugins).
3. Make all changes from the database as a set of transformations.
When switching to a new version, for example 0.2, diff the code between version 0.1 and your custom version based on 0.1 - you will get a list of changes that need to be applied to the new version 0.2 code.
As a result, you will need to roll all the transformations to the database and apply all the changes to the code.

It can be problematic to manually roll changes into the code, especially if there are significant changes in version 0.2.

zy Please do not kick for the lamer question - I have not yet encountered the use of other people's cms. Nothing was found on the subject.

Answer 1

If you significantly finish it, then you need to take not a CMS, but any stable and familiar framework, and do it on it. It is better to ask the creators of CMS how to expand CMS, they should have worked out options (although the number 0.1 does not lead to optimistic thoughts on this matter :) ). Although, in general, something like this, it's just that specific files and schemes of work will be different for different CMS.