Problem/Motivation
This is a follow-up for #218755: Support revisions in different states, which added API support for content moderation in Core. The related UX/UI implementation was left to this issue to solve.
This also aims to solve confusion around our existing UI for saving/publishing nodes (see #1123696: Does 'Save' publish my content? for details), while implementing the new "save as draft" functionality. The physical separation between the 'Save' button and the 'Publish' checkbox make it difficult for users to understand what will happen when they press the button.
Proposed resolution
Initial requirements include:
- After clicking the 'Save' button, you should always see the text you just edited.
- There should be a visual indication of the state of the revision you are viewing.
- When you click 'Edit', you should edit the text of your most recent revision by default, and there should be a visual indication this is happening, but you should be given the option of editing the currently published revision instead (or any other revision).
Remaining tasks
- Settle on resolution
- Implement changes
- Update documentation
User interface changes
Under discussion...
API changes
A number of methods must be added to entities, to support the concept of an edit revision. See comment #74 for details.
References
Related modules
Original report by yoroy
Follow-up for #218755: Support revisions in different states:
You should see the text you just edited after you click the save button, and it should be given some sort of visual affordance for "draft mode." When you click "Edit," you should edit the text of your most recent revision, along with a visual affordance to let you know this is happening, and give you the option of editing the currently published revision instead.