You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It occurred to me maybe this hamburger is a little too cryptic and subtle. Of course it only takes one click to know what's in there, but considering how important start and stop are to an instance (for example), they're pretty buried in the current design.
Here's one idea (adding text to the button instead of a simple hamburger [kebab]), but really there's a whole range of possible solutions, for example pulling out dedicated start and stop buttons at top level. A hamburger is more legible as a ...rest kind of thing than as the place where these actions live.
The text was updated successfully, but these errors were encountered:
Still unsure as to whether we have a single button that switches between start and stop, or two. Two of course take up more space, but give further context when they are enabled/disabled. Also having a changing button will change width as it switches from Start to Stop which may or may not look funky.
Connect gives us a direct line to serial console which is a nice QoL improvement.
It occurred to me maybe this hamburger is a little too cryptic and subtle. Of course it only takes one click to know what's in there, but considering how important
start
andstop
are to an instance (for example), they're pretty buried in the current design.Here's one idea (adding text to the button instead of a simple hamburger [kebab]), but really there's a whole range of possible solutions, for example pulling out dedicated start and stop buttons at top level. A hamburger is more legible as a
...rest
kind of thing than as the place where these actions live.The text was updated successfully, but these errors were encountered: