Once a Content Type is modeled, it should be clear how to modify it over time, while maintaining integrity of existing content.

Keep moving away from dialogs/apps as the implicit model for customer data. Offer tooling for it to evolve over time, with assisted bulk-changes and without Java version handlers.

Example story: As a project developer, I can declare changes to my content types models, so that pre-existing content can be migrated or "adapted", e.g. rename properties, add new properties with a default value, etc.

TBC