Skip to content
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

[Dashboard] Allow Projects for Individuals #4920

Closed
svenefftinge opened this issue Jul 23, 2021 · 3 comments · Fixed by #4966
Closed

[Dashboard] Allow Projects for Individuals #4920

svenefftinge opened this issue Jul 23, 2021 · 3 comments · Fixed by #4966

Comments

@svenefftinge
Copy link
Member

svenefftinge commented Jul 23, 2021

We should allow projects below individual accounts as well.

  • Individuals might feel squeezed into the concept of a team
  • will make teams and individuals more alike and therefore easier to grasp

Designs

BEFORE AFTER
Personal Account - BEFORE Personal Account - AFTER
@jankeromnes
Copy link
Contributor

I'll give this a try! 🔧

@jankeromnes jankeromnes self-assigned this Jul 26, 2021
@svenefftinge
Copy link
Member Author

@gtsiolis WDYT about reversing the tabs, I.e. make project the first one?

@gtsiolis
Copy link
Contributor

gtsiolis commented Jul 26, 2021

Makes sense! Updated the screenshots in the issue description. Cc @jankeromnes

🍊 🍊 🍊 🍊

Cross-posting some notes from the relevant discussion (internal) regarding URLs.

George: Could be minor but going with a) Projects as the first tab here and b) the redirect to /username/workspaces, would lead users the second tab when loading the dashboard using /workspaces their browser history until their browser history is updated based on usage.

George: Thinking about this again, a boring (simple) solution could be to just keep the same URL (/workspaces) for workspaces associated with the personal account and only nest team workspaces within a /team-name/workspaces URL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants