[wp-trac] [WordPress Trac] #39896: Customizer: Allow users to Draft changes before Publishing

[WordPress Trac]

#39896: Customizer: Allow users to Draft changes before Publishing
-------------------------+------------------
 Reporter:  melchoyce    |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  4.8
Component:  Customize    |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  ui
-------------------------+------------------

Comment (by melchoyce):

 > Given that I like the linear approach that is posted above, its
 structure also inspired me an idea that can allow some more advanced
 future features. It basically uses the same interaction on the side of the
 publish button, but instead of opening a small popup takes over the entire
 sidebar. With that space, we can do many things.

 Thanks @folletto, this is a great exploration — I can see it extending
 well to future iterations. For example, this would be a good framework in
 which to add scheduling. Let's explore future after i1 is in the works.

 > I think it could be good to prototype both ways and explore them as they
 are different enough for that.

 @karmatosed: For now, we're just going to focus on drafting vs.
 publishing. We'll explore more advanced options in future iterations.

 > Question: How would a user abandon the changes? How would they clear out
 the draft? Should there be another option in the dropdown to
 revert/reset/trash the changeset?

 @westonruter: This is where I diverge from your thoughts on technical
 implementation. I think drafting here should mirror how it works in posts.
 Specifically, I disagree with:

 > After you hit Save Draft, and then leave the customizer, if you come
 back to click Customize and go straight to customize.php you would get the
 previous drafted changes restored.

 This is how I see it:

 1. Make some changes
 2. Leave the Customizer without saving
 3. Changes are autosaved
 4. Come back into the Customizer
 5. See a prompt to restore changes
 6. If you click to restore, they're loaded into the Customizer
 7. If you click the close icon on the autosave changes notice, the old
 changes are discarded (but maybe saved in your revision history?)
 8. If you make new changes and save, the old changes are overwritten

 We wouldn't load your autosaved changes, but would instead rely on you to
 manually bring them back. I think this is far less complicated than
 automatically loading your autosaved changes, and more consistent with how
 drafting works elsewhere in core.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/39896#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform