Exploring making the end of the publishing flow more noticeable

[karmatosed]

In the past we have looked at things like adding an image, or other identifications. I'm pulling this out into an issue as have some more user evidence now that the flow is feeling incomplete.

With the move to JavaScript, clicking the Publish or Update button doesn’t trigger a page reload. Without that visual cue—and with the new two-click publish workflow—just about all of the users we tested were initially unsure of whether their work was really published.

This comes from: https://design.oit.ncsu.edu/2018/02/02/gutenberg-testing/

Gutenberg requires two clicks to publish, which is already different. After clicking the second button, there’s no page reload, leaving some users unsure of whether it actually published.

Here is the visual flow so far:

There are visual changes but if the above isn't being noticed, what can we do to improve it? I'd love to get some ideas and sketches around this from people.

[afercia]

Related: #4187.

[karmatosed]

I am closing this as we have a few things added recently and #4187 exists and is open. We can review this based on feedback after that is in place. As with anything we can always reopen.