Why does this make sense?
We generally write content in this order - top-->bottom, left-->right, which is the default visual flow. And it is only after we are done with our draft/content for the page we publish the page, which is why the option is listed on the bottom right corner of the page with the others.
Even when you look at any UI design, you see Save, Cancel, Submit buttons at the bottom of the page.
Hope this explains!
Thanks
Sireesha
My question doesn't have to do with the location at the bottom. It has to do with Publish and Close being conveniently exposed and clickable, yet in order to Preview or Delete (or even discover that you have those options), you have to click on three dots to open a menu. I don't see why that makes sense.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi again @Brian Desany
Publish and Close are primary and secondary CTAs (Call To Actions) and so they are made visible to the users. The others are not visible because, they might not be very frequently used as @Petr Vaníček mentioned and if they are made visible they can:
Also, there can be more actions Atlassian is going to add in the future, in which case the bottom of the page is going to get busier and very hard on the eye.
If you look at the header (top right) of any Confluence page you see this -
This again has got most commonly used actions outside ellipsis (...) and all other options within. And so the same design pattern is repeated in the bottom of the page for consistency (I think :) ).
Hope this is what you are looking for!
Thanks
Sireesha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not sure why Preview wouldn't be frequently used, but I suppose that's a matter of personal style and preference. On the other hand, having 2 visible options and 2 not-visible options, when there is a ton of space *right now* still seems silly. Of course if it were really functional, users could expand and contract it, reorder the items, and any lesser-used items would be hidden only if there was not enough room for them. Like the bookmark bar of Chrome for example. I know that's never going to happen, but I hope you get my point. There are innumerable aspects of Confluence that reflect these kinds of static design limitations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Based on my opinion - because these buttons are rarely used and usualy are used on Publish and Close.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.