Skip to content

UI: Add notices for published, updated, save failed #967

@jasmussen

Description

@jasmussen

Splitting this out from #707. The flow for publishing and saving is soon in a good place.

We have, however, a need for a few edgecase notices:

  • Published successfully
  • Updated successfully
  • Scheduled successfully

... as well as failure states:

  • Publishing failed
  • Updating failed
  • Scheduling failed

... and also for draft saving and auto saving:

  • Save failed

Save Failed

Let's make this part of the "Save" area on the left:

saving publishing

Publish/Updating/Scheduling notices

We'll probably want notices after all (see also #486), because thankfully we were able to test for a while a design where the notice itself was integrated in the button. Not only did this feel ephemeral, but it made the button itself feel more complex. It also doesn't work that well if we ever get to exploring a dropdown button as suggested in #708.

So here's how notices could look:

notices

Metadata

Metadata

Assignees

Labels

General InterfaceParts of the UI which don't fall neatly under other labels.[Focus] Accessibility (a11y)Changes that impact accessibility and need corresponding review (e.g. markup changes).[Type] TaskIssues or PRs that have been broken down into an individual action to take

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions