Consider differentiating external links from internal links in the dashboard
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
By default, any (internal) links that keep the user within Gitpod open in the same page rather than in a new tab or window. Currently, the dashboard includes internal links but also external links to repositories, branches, etc and this can sometime become confusing as 🅰️ there's no clear differentiation of those links and the expected interaction as well as 🅱️ the design of those links can sometimes be inconsistently the same as internal links which could surprise users. 🎁
@AlexTugarev recently mentioned this during a deployment, see relevant discussion (internal).
Proposal
We could consider:
- Limiting the amount of external links as much as possible, or especially avoid using the same design with internal links
- Introducing an external links icon that can be shown at the end of the link text
- Consolidating the design of the links so that it's a bit more clear when a link is an external link across the product
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
No files, tests, or dashboard entry points are named. Start by reviewing the dashboard's internal and external link usages and the proposal's three options; done means an agreed, consistent visual distinction and expected interaction for external links across the product.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100