Content type modification and model lifecycle

Questions and Answers
1
System Information
  • Strapi Version: 3.6.5
  • Operating System: Linux
  • Database: MongoDB 4.0.10
  • Node Version: 12.22.12
  • NPM Version: 6.14.16
  • Yarn Version:

Hello

I would like to validate the correct lifecycle for content types.
When adding a new content type on local environment, strapi automatically generate endpoints for it, with routes, controllers, model and services. Those can be modified to add logic, and then committed.

First question: when application is deployed in production, is it mandatory to re-create the content type, or will strapi automaticlly create the content type based on /api/**/ content?

Now we wand to modify the content type, by example to add a new field. This can be done directly in Production, but I guess that’s not a best practice, for codebase will not be updated.

Second question: so does that mean that every content type modifcation should priorly be made in local environment, so for example api/**/models/{content type}.settings.json is updated?

Thanks for your help