Dashbard UX enhancement suggestions

[marcusquinn]

@nebulon Nice. If it's a button now, rather than a drop-down, that makes more sense to use an icon representing the destination.

Personally, I'd prefer the single-cog icon here and for the Service menus, if you'd consider that?

• https://fontawesome.com/v4.7.0/icon/cog

[nebulon]

@marcusquinn agreed, using the single cog now

[hexbin]

@nebulon Awesome improvements!

given that we haven't done any visual focus handling

Unfortunately it's a very widespread bad habit among web designers to unconsciously style only :hover states. By omitting :focus, accessibility is actively reduced. Not blaming anyone. You might want to check if your CSS files serve this finding.

The defaults are not always a good fallback. Not many people actually know that they could adjust their system (not even many among those who rely on assistive technologies). When we avoid touching the way the defaults do the styling (e. g. outline) we can still do a lot for accessibility

[hexbin]

Now that we've satisfied some basic power users' needs - mind if I get back to the original motivation (description field, login type)?

At least once a week I have to tell an app-using team member that it's not their fault and to stop blaming themselves (no, you are not "too stupid").

It would be such a blessing to help non-admins help themselves.

[nebulon]

@hexbin said in Dashbard UX enhancement suggestions:

The defaults are not always a good fallback. Not many people actually know that they could adjust their system (not even many about those who rely on assistive technologies). When we avoid touching the way the defaults do the styling (e. g. outline) we can still do a lot for accessibility

so we are on track here, I've added the darker outline, but the native one is still inset of that. I have not restyled this (not visible in the screenshot, as real focus went to the screenshot tool )

[A Former User]

@nebulon That looks so much cleaner! Thanks for your hard work!

[d19dotca]

@nebulon said in Dashbard UX enhancement suggestions:

You can see the stop/pause action also being more prominent up there now.

It's looking like a great improvement, thanks for the hard work and for taking all our feedback into consideration.

Just two quick questions:

1. Is there any intention to add the Restart button too, or is it only a stop button (which I assume then translates to a start button when stopped) for now? I suppose the restart button isn't as necessary now since it's also in the File Viewer area which is generally when we'd need to restart an app anyways after editing a file. Though I still like the idea of sticking to how operating systems UI are done, where the shutdown and restart buttons are next to each other.

2. Is there an "are you sure" pop-up when clicking/tapping the shutdown/pause button to avoid miss clicks?

Bonus question: Should the shutdown/pause button perhaps be the "Power-off" icon instead of the "Pause" icon? I guess it could work either way, just thinking the Power Off one may make a little bit more sense at a glance.

[marcusquinn]

@hexbin wondering if login-type icon might be better in the top-left now to balance the cog top-right?

[hexbin]

@marcusquinn Sounds like a good idea. I'm sure we can trust the wonderful Cloudron team with design decisions (and weighing those against technical feasability).

As long as they can make this happen - nag, nag

[nebulon]

@hexbin ok I did some attempt there and we now show such an icon with a tooltip for non-admins. Admins should know already, as well as they can get that info in the app detail view. Always showing them felt a bit too cluttered.

[marcusquinn]

@nebulon Very nice! Can you post the text for each? I like wording things, and context helps

[hexbin]

@nebulon Aaaawesome! The tooltip solution is closer to where it's needed, good. (But be aware of possible accessibility implications.)

[hexbin]

@nebulon Any progress with the description field yet?

[nebulon]

The tooltip text will be finalized in weblate due to translation, will push this in a bit.

For the description, we won't do this right now as it has various text-length issues and we already have tags and the option to give descriptive names, which already indicated in this thread can also be used to clarify to some extent. In the end this would be just the same with the same visual space limitations as the app name field, so I am not sure where the benefit is, besides limiting space even further due to more fields.

[jdaviescoates]

@nebulon great stuff!

but re:

Admins should know already, as well as they can get that info in the app detail view. Always showing them felt a bit too cluttered.

Personally I'd like to see it as an Admin too (if you've got loads of apps it's hard to remember how each is set-up)

[d19dotca]

@jdaviescoates Agreed. Likely not an issue for a server with only a few apps, but can be a quick time saver for that at-a-glance info when hosting many of them. I'd personally like to see a toggle that allows this for admins so that it's not there for people who don't want to see them. But that can always be second iteration. haha.

[hexbin]

I love you

[marcusquinn]

The Running / Stopped text sticks out more like a sore thumb now

[marcusquinn]

I tend not to use this on mobile, but still using rollover suggests that issue isn't covered with this update?