Gutenberg: Consider Notices

[jasmussen]

Current look:

Let's discuss what's best to do here.

[youknowriad]

I've always found that these notifications are too intrusive. Is it the time to start considering notifications in the Admin Bar (similar to Calypso)? This could be a separate project I guess.

[jasmussen]

I've always found that these notifications are too intrusive. Is it the time to start considering notifications in the Admin Bar (similar to Calypso)? This could be a separate project I guess.

Agree completely, but that's probably a separate project.

Regardless it's something we have to consider. Because when you publish, you'll need a "Published" notice somewhere. I have some ideas, but wanted to open the floor also.

[inhll]

There's a good opportunity to place notifications in the Editor Bar...

The number of waiting notifications could also be shown. I do agree with @youknowriad that system updates would be better shown in another location, but used them here because... placeholder!

[rileybrook]

In thinking about the publishing notification, and not other notifications:

when you publish, you'll need a "Published" notice somewhere. I have some ideas, but wanted to open the floor also.

The publish button element itself could indicate the successful action to the user. Changing from blue to green, then back to blue could reduce screen real estate taken up by a notification that their content has been published successfully.

[jasmussen]

@inhll

There's a good opportunity to place notifications in the Editor Bar...

Good exploration, thank you!

I'm not convinced that putting them in the editor bar is a good idea, mostly from a "why is it different from the rest of the admin" and space concerns. We likely can't remove the visual/HTML switch from there, as that has to have top hierarchy placement. And the "Saved" indicator will likely at times spell out "Draft [Save]" or even "Saving". Maybe that's not too much space extra, but combined with various translation lengths of the toggle buttons, the ability for plugins to add buttons to the top right action button area, and responsive, it just doesn't seem a scalable area.

A question we also have to ask is: how many notifications are we likely going to see i the editor? @rileybrook taps into something interesting here, rethinking what those notices are. "Published" solves half of it, and if we combine this with a permalink affordance somewhere (perhaps next to Saved? perhaps inline in the body itself?) we have arguably the most important notice of the editor addressed.

The update notice — perhaps we don't need to see that on _every_ screen in the admin. Perhaps the editor can be the first exception?

Or maybe it can be a floating, dismissable notice?

Good thoughts, let's keep thinking.

[joyously]

Wouldn't this be the same area used by plugins for notifications?

[inhll]

The feedback is on point @jasmussen -- and I like @rileybrook's approach to the problem! Perhaps a mix, where "publish" is no longer a notification but instead integrates with the button as @rileybrook showed, while actual notifications appear similarly to how they do now?

The floating dismissable notice / notification / toast message is definitely a good option and is pervasive because it works well!

[mapk]

I like @rileybrook's take on the published notice. My first thought was how would the button change back to 'publish' again, but then I realized that the button could change back when something is edited on the page. So this works well, I think.

[joyously]

I was just reading through the Roles and Capabilities page, and it says that the publish_posts capability is needed in order to see and use the Publish button. Otherwise they can only save drafts. Does this affect how the notice works?

[jasmussen]

Otherwise they can only save drafts. Does this affect how the notice works?

It does, but a good solution might be to simply change the publish button to a Save Draft button in that situation.

[jasmussen]

Closing this in favor of #707. We can always reopen if need be.