Melito In my organization, we often need to go into a page to understand how it was built -- check headings, alternative text, etc. There's not a simple way to do that other than checking the page out to take a peek under the hood. In the land of Discard changes, we could do that without forcing the page back into draft with no edits. It would continue to show as published. I would check heading sizes of text, to be sure things open in a new tab, etc. If everything looked good, I could hit Discard changes and it was all good. My hundreds of editors often do the same thing, and some even hit "edit" accidentally and don't make any changes. My internal communications team often will make edits to try out new layouts or to see if they can add more content to a page (to see if a new page is needed) and will abandon their edits. I have hundreds of decentralized editors who cannot handle the word "Draft" as a status. At first I was getting 30-50 pages a week in workflow with no changes simply so they saw "Published" instead of "Draft." I have customized workflows with paid subscriptions so having content with no changes coming through costs my organization money. My team did a ridiculous amount of education about Discard changes to stop that from happening, and now we're down to 2 or 3 pages a month coming through workflow with no changes. I cannot unleash reverting using version history. It's not a concept the casual user can manage, and I have many people who work in sites daily who will not be able to manage it. I am in an industry where accuracy is absolutely paramount. If the wrong version of some content is published, it could lead to someone being physically harmed or killed. I can't have casual users reverting versions on their own, and I don't have the bandwidth to handle that on their behalf 50 times a week.
Is there some way you could make the Discard changes option available if only a single editor has made changes or to only discard one person's changes if they're using co-authoring?