Use a different favicon based on workspace status
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
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 (https://github.com/gitpod-io/gitpod/issues/4225), they are still a good next iteration and can be improved later on.
Re-posting from https://github.com/gitpod-io/gitpod/issues/7477#issuecomment-1141049961:
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
Alternatively, we could introduce toned down favicon icon form the error and stopped phases.
Error Stopped & Timed out
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing workspace status icon used in the workspaces list and the favicon handling for the website, dashboard, and workspaces. Compare the proposed states and decide which status-to-favicon mapping is in scope; done means the favicon reflects the workspace status in each relevant interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100





