Skip to content

Use a different favicon based on workspace status #13837

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

Open
gtsiolis opened this issue Oct 13, 2022 · 3 comments
Open

Use a different favicon based on workspace status #13837

gtsiolis opened this issue Oct 13, 2022 · 3 comments
Labels
aspect: accessibility meta: never-stale This issue can never become stale type: improvement Improves an existing feature or existing code

Comments

@gtsiolis
Copy link
Contributor

gtsiolis commented Oct 13, 2022

Problem to solve

The Gitpod logo is used as a favicon for the website, dashboard, and workspaces regardless of workspace state.

Given the upcoming changes with the usage-based pricing, having a better view of the running workspaces which consume credits or errored workspaces that need attention could be useful to provide better 🅰️ visibility of system status and 🅱️ user control.

Proposal

Let's update the workspace favicon based on the workspace status.

We can use the existing workspace status icon used in the workspaces list to mimic this behavior. Although these icons are not quite accessible (#4225), they are still a good next iteration and can be improved later on.

Re-posting from #7477 (comment):

A boring (simple) solution as a good MVC (minimum viable change) for resolving this could be updating the favicon based on the workspace status or start phase. Title is used to indicate the status, not intended for implementation.

Running Starting, Stopping, Timing out Error Stopped & Timed out
favicon favicon Favicon 4 Favicon 8

Alternatively, we could introduce toned down favicon icon form the error and stopped phases.

Error Stopped & Timed out
Favicon 5 Favicon 9
@harshsinghatz
Copy link
Contributor

Hey @gtsiolis, Can I work on this??

@gtsiolis
Copy link
Contributor Author

Absolutely, @harshsinghatz! Feel free to open a pull request and link back to this issue.

@stale
Copy link

stale bot commented Jan 16, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Jan 16, 2023
@gtsiolis gtsiolis added meta: never-stale This issue can never become stale and removed meta: stale This issue/PR is stale and will be closed soon labels Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aspect: accessibility meta: never-stale This issue can never become stale type: improvement Improves an existing feature or existing code
Projects
None yet
Development

No branches or pull requests

2 participants