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

 I think we're starting to move away from the right solution here, the more
 we focus more on changesets and less on drafting.

 For example, the trash can — I've asked a couple people this morning what
 they think it does and I've gotten a range of answers:

 > Deletes my site

 > i would expect every change i'd made since the last time i clicked Save
 & Publish to be reverted. i could also see how some might expect it to
 revert every change they'd made since entering the Customizer in that
 session, even if they clicked Save & Publish at some point.

 > I don’t think it would delete my site, which is my gut reaction. That
 option being disregarded, I would guess it means that I lose the changes
 I’ve been working on. but I don’t know what to guess. I’m confused mainly.
 I’m confused because it’s an odd mix of interactive customizer work and
 change/save work. if the publish button is there, I expect that to be
 “save”, trash as “cancel” - but if I don’t save, I also expect to lose my
 changes

 > no idea! maybe “delete all my customizations and revert back to
 default”? but that’s really just a guess. and I don’t think a trashcan is
 a good icon for that action. trashcan means “remove/delete” there is
 nothing to delete  in the Customizer, that’s the problem - they’re just
 settings

 > I would imagine the changes would not be saved. If I’d made changes to
 anything I would expect those changes to be reset, but I would not expect
 any previously saved/published changes to be reverted. And if it
 matters/helps - I would only expect previously saved/published changes to
 revert to the original state with the use of a button/command labeled
 “reset” and a confirmation modal. Anything less would enrage me. Well, as
 much enraging as I do these days which is more of a FFS.

 > great question. `x` feels like it would close + cancel my changes. if i
 had an element selected, i would think the trash would delete that? but
 feels weird to be way over there next to the publish icon

 > Hm. I hope it wouldn’t delete my site. But there’s a publish button next
 to it. But I’m working on my site, not a post. Maybe it would delete any
 changes that I had “customized” but not yet published? Kind of like a
 reset back to the latest saved version?

 This is one of the reasons I'm still struggling to wrap my own head around
 changesets. They seem like revisions with superpowers, and even regular
 post/page revisions can be a little confusing in WordPress. Changesets
 seem to be bringing in yet another layer of complexity to a tool which is
 already quite difficult for newer users to figure out.

 Let's think about the user experience of drafting changes to your site
 design, without assuming that Customize Snapshots is the correct solution.

 If we didn't already have this idea of changesets, is this how we'd design
 this feature? If the previous proposal is too complex for 4.9 — which is
 fine, I'm cool with reducing scope — then let's focus on doing one thing
 really well. Using concepts that most people will be able to understand
 without prior experience will help us accomplish that.

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