search

websemantics / stone-theme

:moyai: Responsive admin theme for PyroCMS 3 that's easy to install and customize, with slick ui and intuitive user experience.
MIT License
13 stars 2 forks source link

Thoughts on moving section buttons over to be closer to where the other action is? #8

Open RyanThompson opened 7 years ago

RyanThompson commented 7 years ago
screen shot 2016-11-15 at 2 38 47 pm
websemantics commented 7 years ago

Sorry for the delay,

Actually, this is a great discussion to have, .. I've seen few products UX guidelines (should Pyro have one?), for example,

And I yet to see something I like,

In this scenario, action buttons should be grouped based on context (module, entry, etc), which is correct here, however, there are some inconsistences overall when it comes to Form actions (wording, location etc),

Plus what I think can be done is probably more UI streamlining, (bring things closer in relation to space / proximity) like you suggested, but then Form actions can't appear on two locations as is the case now,

RyanThompson commented 7 years ago

I would love to create a set of principles! I love principles!

The argument in favor of duplicate actions is that it's easier to use the closes action rather than scroll all the way up or all the way down again.

websemantics commented 7 years ago

Here's a starting point, https://docs.vanillaframework.io/

UX principles go even deeper, .. into voice and tone, check this great example, http://voiceandtone.com/

I understand it's convenient, but it's not conventional, users - ahem - usually expect Form actions to be at the bottom, right/left aligned. This is not to say it can't be elsewhere if needed. The problem I see with having them at both ends is, first, you lose that space (top in this case) to express things other than form actions.

Also, notice how the top group has an extra function (choose language), they should be identical if need to keep both, in my opinion,

Have you seen this, http://www.goodui.org/ ... words can't describe how awesome these suggestions are ..

websemantics commented 7 years ago

On more thing,

I think the problem you were trying to address by conveniently providing Form actions at top/bottom of a page is long forms where the issue of scrolling becomes apparent,

This is yet another UX/UI challenge that can be solved differently with for example, folding pattern (show/hide), wizard pattern, tabs etc.

Preferably, all form elements should fit onto the screen (desktop mainly) and Form actions are visible already or can be with fewer scrolls, assuming they only appear at the bottom of the form,