Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make resource actions on detail page more discoverable #2419

Open
david-crespo opened this issue Sep 9, 2024 · 2 comments · May be fixed by #2508
Open

Make resource actions on detail page more discoverable #2419

david-crespo opened this issue Sep 9, 2024 · 2 comments · May be fixed by #2508
Labels

Comments

@david-crespo
Copy link
Collaborator

david-crespo commented Sep 9, 2024

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.

image
@benjaminleonard
Copy link
Contributor

Something like this?

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.

Image

@benjaminleonard
Copy link
Contributor

See alternatively:

Image

@benjaminleonard benjaminleonard linked a pull request Oct 17, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants