Specific 404 handler for teams (& projects)

[geropl]

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 www subdomain), to be self-contained

[stale]

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.

[gtsiolis]

thought: Probably a good improvement with small impact.

suggestion: Potentially breaking this down to smaller scoped issues with clear action forward and designs to implement could help.

Cc @jldec

FWIW, we already redirect some 404 pages to the website. For example:

1. Non-existent team: https://www.gitpod.io/t/xyz/

However, many inner pages still do not contain proper information. For example:

1. Non-existent project: https://gitpod.io/t/gitpod/non-existent
2. Non-existent prebuild: https://gitpod.io/t/gitpod/gitpod/non-existent-prebuild
3. Non-existent project page: https://gitpod.io/t/gitpod/gitpod/non-existent-project-page
4. Non-existent project and project page: https://gitpod.io/t/gitpod/xyz/non-existent-project-page
5. ..