>>! In T44138#3579770, @Jan_Dittrich wrote:
> From observing the users and further corroborated by the comments on Kurier 

Some notes on the different observations:

> 1. Users, particular experienced ones, seem to rely a lot on previewing before they save, so they want to preview //before// they save and create an entry in the history.

This probably means that some users don't see preview as part of the publishing process, but as part of their edit process: edit-> preview -> continue editing...

> 2. In the current UI, the only way to preview is clicking a button that indicates it does something they want to avoid: Saving directly.

Having the option to preview as you publish is fine, but it does not have to be the only entry point we provide for it. Especially if we want to support users that don't see "preview" as part of the publishing process. for example, we can provide an access to preview as an additional mode in the menu we provide access to "Visual editing" and "Source editing". That seems to align better with the idea of supporting preview as another perspective to switch while editing. 

> Thus there is a problem. Adding … does not solve all the problems. But it alleviates point 2: It indicates that clicking "publish changes" does //not// do immediately what they want to avoid. 

I don't think that adding ellipsis is going to alleviate the issue of point 2 since the publishing button (with ellipses or other indications) has the main job of announcing the path to publishing, and being it in one or two steps, these users are not interested to go into it yet. Making the "publish" action (even slightly) to be less about publishing does not seem the most promising option.

Let's assume that ellipses make more users access the summary panel. Is that solving the issue? I don't think the problem is that those users are not reaching the summary panel, these users probably have already done so (since they are experienced editors), the problem is they don't seem to find it natural to go through the publishing path while their editing process is not over.

I'm ok with experimenting with this if people think it may have potential, but let's make sure it does not impact the regular use of publishing when people actually want to publish.