[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 westonruter):

 @melchoyce I don't really see how changesets are being newly in focus
 here. I think it's even less about changesets then previous designs
 because it's the linear model discussed above. (There's no branching
 changesets shown, or UI for managing multiple changeset drafts
 concurrently.) It's just giving user control over managing a single draft
 of changes to the Customizer, being able to get back to the changes they
 were making before, and be able to eliminate/revert the changes to start
 over.

 The trashcan icon was intended as a way to just abandon the changes you've
 been making, to start over. It's the reset/revert/start-over. That wasn't
 accounted for before in the Customize Snapshots plugin either or in the
 Customizer generally. Maybe a revert/undo icon would be better.

 Otherwise, I don't see the new mockup scenarios as being much different
 than what was previously designed, other than being a subset of the
 functionality in the most recent designs: no “non-linear”/branching
 changesets, no scheduling, no revisions list, and no new panel with
 options to open. To me it does seem like it is focused on doing one thing
 really well: drafting changes.

 ----

 I agree that (branching) changesets are indeed like like revisions with
 superpowers. Actually, it's essentially the “post forking” concept that
 was popular for awhile, but for forking changes to your entire site
 instead of for a single post and then merging the changes back to go live
 on the published site instead of the original post. That is a hard thing
 to newer users to grasp, so maybe it should remain in a feature plugin
 like Customize Snapshots if we can never find a way to add it to core in a
 way that makes sense for the majority of users. That may mean that
 scheduled changes never come in either, since really having a scheduled
 change somewhat precludes there being multiple concurrent changesets
 (branching/non-linear) since you'd probably want to new draft changes
 while you have a previous set of changes already scheduled.

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