[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                          |  westonruter
 Priority:  normal                               |      Status:  accepted
Component:  Customize                            |   Milestone:  4.9
 Severity:  normal                               |     Version:
 Keywords:  has-patch needs-testing needs-unit-  |  Resolution:
  tests                                          |     Focuses:  ui
-------------------------------------------------+-------------------------

Comment (by westonruter):

 @sayedwp In coding up the UI for this, I suggest:

 * Create a new branch independent of the autosave work being done in the
 existing [https://github.com/xwp/wordpress-develop/pull/256 PR], since I
 do not think there are any key dependencies (other than a needed filter
 for configuring whether or not multiple drafted/scheduled changesets can
 exist concurrently).
 * Register a new section for the “Publish Settings”. The priority can
 perhaps be `0` with the `themes` section getting bumped up to `1`. In
 reality, it shouldn't matter the priority because I'm thinking that the
 “Publish Settings” section item wouldn't appear at all in the list of
 sections. It should instead be hidden, as the way to expand it would be
 via the gear icon next to the Publish button.
 * The header for the publish settings section would get a back button that
 appears on the right with an upward arrow. See [41368] for how a right-
 facing arrow was added for the Themes section. I don't think we're all
 completely confident on this upward-facing button here (as clicking the
 gear icon again would also collapse the panel), but it's something we can
 try.
 * It would be a great if the section expanded downward instead of sliding
 from the left (as Themes) or right (as everything else).
 * The action/status radio buttons and scheduling datepicker can all be
 part of a single custom [https://make.wordpress.org/core/2016/03/10
 /customizer-improvements-in-4-5/ setting-less control]. Or I suppose it
 would be best if the control actually could be connected with the
 `wp.customize.state( 'changesetStatus' )`, but that would depend on
 #37964. It would just be important to ensure that the control's state is
 linked with `changesetStatus`, so that if the `changesetStatus` changes
 programatically by a plugin that the selected radio also changes. There
 should likewise be a `changesetDate` state that is linked to the date/time
 picker. I believe you've already implemented something like this in the
 Customize Snapshots previously.
 * The share preview link would be in a separate setting-less control.

 All of this should be pretty familiar to you with your work on Customize
 Snapshots. Your experience with that feature plugin will also be key to
 identify areas in the core implementation where we need the hooks to
 ensure Customize Snapshots can continue extending the core UI to add the
 “power user” features, like being able to have multiple changesets drafted
 at a time, being able to give titles to changesets, and so on. 🙌

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