Specific 404 handler for teams (& projects)
Open
Nobody has claimed this yet.
component: dashboard
feature: admin dashboard
meta: never-stale
team: webapp
type: improvement
user experience
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
A general 404 redirect to www.gitpod.io (away from the webapp) is bad for UX because if user mistype/miscopy/don't have access to a team (or project) they end up on the webpage. This is not a dead-end per-se, but definitely feels arkward and requires additional mental work to get back.
Would be nice to distinguish between:
- looks like a team URL:
- "team does not exists or you don't have access"
- actions:
- create (same as /new with preset name from slug)
- maybe "request invite"?
- could be a project URL:
- if team does not exist: same as above
- if team exists but project not:
- "projects does not exist. want to create/import?"
- actions:
- create new
- import
- nothing of the above => redirect - or even better: have a 404 within the webapp (not
wwwsubdomain), to be self-contained
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 tracing the webapp's current general 404 handling for team and project URL patterns. Define the expected behavior for missing or inaccessible teams and projects, including available create or import actions, and verify that unrelated paths retain the intended redirect or in-app 404 behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100