Site building mode - Provide means to differentiate between working on the site (site building) vs. working in the site (content management)

Problem/Motivation

Drupal has a concept of differentiating between configuration and content. We currently explain this mostly by where we put things and who has access to them but often, I see myself needing to explain the difference in very technical terms that aren't clear to the person logged into the site.

Steps to reproduce

Login as administrator, open taxonomies, there's no easy way to know that "Taxonomies" are configuration which is stored in the file system and needs to be deployed, vs. "Taxonomy terms" are content that is stored in the database.

Proposed resolution

An idea that comes up is to introduce a site building mode:

* By default, site building mode is off but anyone with the permission to edit configuration can enter site building mode
* By default, configuration changes will ask you to confirm entering site building mode first. This way we could explain the consequences (i.e. need to export config when working in different environment). I.e. when you open the edit form of a taxonomy or content type, it would show an indicator that informs you that the form will touch configuration. Once you submit the form, it will ask you if you are ok with the consequences / want to enable "site building" mode
* For experienced site builders, they might want to have an option to enable site building mode all the time or skip this verbosity

Remaining tasks

This is just a rough idea so far, so coming up with feasibility inputs and some wireframes might be the next steps collect feedback and validate the idea.

User interface changes

tbd

API changes

tbd

Data model changes

tbd