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

 Hi people! Sorry for my delay in replying. I've caught up (I hope) with
 the discussion above, and provided a i2 design that hopefully converge the
 point we preferred — in the design however I also introduced a couple of
 differences, so let's review:

 1. The label is changed from "Status" to "Action". I had the impression
 that "Status" wasn't very clear, as it might imply status of... something?
 Given instead it changes the action that the user is about to make
 clicking the button, I thought "Action" would be clearer.
 2. Finding a name is hard. I used in this design "customization" since it
 seem fitting with all the scenarios: it's unique, it's semantically
 meaningful, and it can be paired with other words: "customization draft",
 "scheduled customization", and so on.
 3. I added back the "current live customization" date and author. I think
 it can be very valuable, but feel free to ignore if the data isn't there
 or if you don't feel it's relevant now.
 4. I wasn't sure what the checkmark or the UUID was in the opened
 customization draft: I think the date is already the one above, and I feel
 the URL would be more useful there as a reference, and... isn't the URL
 already the UUID? double win?
 5. I feel the title there adds too much complexity. Why not make the
 customization draft title editable from the list below? In that way the
 default date/time would do, but if more specificity is needed, it's
 something the users could do later. Skipping this for now seems to me also
 matching better the current iteration of the work, but again, maybe not.
 6. I used ••• instead of the chevron as the chevron implies a dropdown of
 some form. This would be a new pattern, so I feel it should be using a
 different icon. That said, it's minor, so if there's a preference for the
 chevron, or the cog as per the latest above, or another icon entirely,
 it's fine too. :)

 Everything else should be as you discussed and mocked... if not I might
 have just missed it, sorry!

 I hope this mockup makes sense. :)

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