Problem/Motivation
The concept of workspaces and site-wide previews apply only to revisionable and publishable entities. However, it is very easy for site editors to miss this point and change some config values in a non-default workspace, for example adding a block in a Stage workspace, thinking that it will not show up in the Live workspace.
Proposed resolution
Figure out a way to communicate this and prevent any changes that would leak into the Live workspace.
Likely candidates:
- config entities/objects
- state
- path aliases
- others?
Remaining tasks
Discuss.
User interface changes
Yes, TBD.
API changes
Nope.
Data model changes
Nope.