[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.9
Component:  Customize    |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:  ui
-------------------------+------------------

Comment (by JoshuaWold):

 Howdy! I'd like to share an update.

 * I've created a [https://xd.adobe.com/view/95393ea0-df5e-4530-878b-
 5dfc39dcf59d/ clickable prototype] based on the design from @folletto
 above and some discussions with @melchoyce and @westonruter.
 * Also, here's a [https://v.usetapes.com/FtPF85zqyL screencast] walking
 through the prototype.

 Would love feedback.

 As of right now here's a few things that need to be done:

 = '''Date picker''' =

 We need to decide whether scheduling in the customizer will follow the
 same convention as the [https://cloudup.com/cq67u87coBl WordPress admin],
 or whether we could improve on that. One of the ideas suggested has been
 to add a date picker.

 Here’s some directions we could take with that:

 * [https://cloudup.com/c54C91U7nyo Calendar date picker] inside the
 Customizer panel (matches how Calypso in WordPress.com works)
 * [https://cloudup.com/ciAq6yyRpoy Calendar date picker] with keyboard
 accessible input, also discussed
 [https://github.com/WordPress/gutenberg/issues/1311#issuecomment-327576243
 here].

 @afercia brought up accessibility concerns about datepickers in general
 and what advantage they offer over default input fields.

 So it seems that any solution chosen should have (at the very least) a
 fallback to entering input fields.

 Open to thoughts on this!

 = '''Save and Publish button flow''' =

 We need to figure out the flow of the save/publish button when scheduling
 a draft. Here I propose how the flow could work:
 https://v.usetapes.com/iBRTo9jNJz. But, based on feedback from Weston, we
 need to consider the following:

 What happens to the grayed out blue scheduled button when a user makes an
 additional change? Doe the button become enabled again or auto-save (not
 desired). The explicit action of clicking the button is how we are able to
 create a revision.

 There’s currently a
 [https://wordpress.slack.com/archives/C0381N237/p1504725296000135 Slack
 thread] in Making WordPress Slack discussing this issue, feedback is
 welcome!

 = '''Wording for Customization/Drafts/Changesets''' =

 There's been some additional discussion around what word should be used to
 define revisions/changesets, etc. Definitely open to playing with the
 word, but I'm concerned that "snapshot" or "revision" might be more
 ambiguous than "Customization". The idea of just not including the word at
 all is interesting (as proposed by Nick Halsey).

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