@mariohamann @gorgonzola
d) For CraftCMS, there is "php craftcms up" for deployment which applies all project config changes (entry type changes, fields) to the live database on deployment. https://craftcms.com/knowledge-base/deployment-best-practices#codify-deployment-steps
I haven't seen that for Statamic. Kirby has the same challenge. What if Developer A does some massive content structure changes and we want to deploy it safely and robust?
As you said - that is a challenge for all CMSes.
Each system and approaches has their strengths and weaknesses, but as far as I know Craft CMS took the biggest step towards "automatically keeping the config and data structure in git" and provide a way to deploy it.
Strapi has it in git, but there is not auto-migration if you change entry fields / do bigger structural challenges as far as I know. 2/