Description
Weakness
The changeNote input field has a minor prominent position in the sidebar like under the preview image text element on a page. To simplify proper editors tasks it should appear close to the save button.
Goals & Features
To fix the UX weakness the field should appear after clicking the Save button at the top left close the position like with other history related tasks (publication state change, sharing etc.)
There could be a configurable option to decide where to show up the input field.
To enforce proper editors behaviour the feature should be opt out only on a per document and /or per user basis including a warning.
Why?
- For professional use cases enforcing change notes is an important feature. Looking into histories without some change notes can be cumbersome to figure out who is responsible to allow resolving of issues or requests.
- in Ticket Copytext of Stories, News, Events mentioning dates in the future is not properly transformed after the event date. How to improve the workflows. plone.de#65 I describe the need to describe the purpose of changes of a page over time to keep track of the state long living content or supporting the lifecycle of an event from future to present and past.
Related issues:
This change was supported by @tisto in this comment and confirmed that this is a Plone core / Volto issue here
In Volto Light Theme the field wrapper is visually hidden. See:
- changeNote input UI field not showing up in edit view when versioning behaviour is active on content type due to CSS "display: none;" #6105 kitconcept/volto-light-theme#488
- ChangeNote Input is missing in Volto VLT edit page template due to CSS display none plone.de#66
Due to lacking skills in React I cannot come up with a PR here.