Add development flow to FAQ

Author: derrickmehaffy

docs/3.0.0-beta.x/getting-started/troubleshooting.md

@@ -22,6 +22,19 @@ Fill out the form on the [Support page](https://strapi.io/support) of the Strapi
 
 ## Frequently Asked Questions
 
+### Why can't I create or update content-types in production/staging?
+
+Strapi stores model configuration files (what defines the model schema) in files such as `api/restaurant/models/restaurant.settings.json`. Due to how Node.js works, in order for changes to take effect, that would require Node to restart the server. This could potentionally cause downtime of your production service and likewise these changes should be tracked in some kind of source control.
+
+Generally your "flow" of development would follow the following path:
+
+- Development - Develop your Strapi application locally on your host machine, then push changes into source control
+- Staging - Deploy changes from source control to a "production-like" environment for testing
+- Production - If no other changes are needed, deploy into production
+- Repeat as needed, it is recommended that you properly version and test your application as you go
+
+At this time and in the future there is no plan to allow model creating or updating while in a production environment, and there is currently no plans to move model settings into the database. There is no known nor recommended workarounds for this.
+
 ### Does Strapi handle deploying or migrating of content?
 
 Strapi does not currently provide any tools for migrating or deploying your data changes between different environments (_ie. from development to production_).