Ghost: Improve usability of unsaved changes dialog

[peterzimon]

Issue Summary

There are cases when the Ghost editor can get to an unsaved state (see 'Steps to reproduce'). These cases are handled with a popup dialog asking the user if they want to leave the editor without saving the changes. It also asks the user to save the changes but there are no instructions for it:

Steps to Reproduce

1. Create a new post
2. Add or remove tags for the post - don't make any changes in the post body, otherwise the system automatically saves.
3. Click on e.g. 'Stories' (or any other link) in the navigation sidebar

While it's possible to save the post by hitting CMD+S or Ctrl+S, it's not communicated properly.

[peterzimon]

Design

The following use cases are treated differently:

1. Post state: draft
   If the post is in 'draft' state then everything should be auto-saved. Tag changes (added, removed tags) should be saved on close of the Post Settings Menu (sidebar)

2. Post state: published or scheduled
   If the post is published or scheduled the following dialog should appear if there are unsaved changes in the post (or its settings) and the user wants to navigate away from the editor:

On the dialog use the following style on mouse over on the destructive action (for stronger feedback):

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[kevinansfield]

Not stale

[MrMovl]

We are testing ghost internally right now, and some of our team are very unsure about the way documents are saved. Having an autosave hint on the top confuses people, because it is argued that changes aren't really saved, when one leaves the editor and clicks Leave.

While it's possible to save the post by hitting CMD+S or Ctrl+S, it's not communicated properly.

And I agree with this. Honestly, the easiest solution (and the one preferred by my team) seems to be an (optional) Save button in the top, left corner. Though I do like @peterzimon design idea and see it as an improvement, it might only be part of the solution.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[kevinansfield]

Not stale

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.