Skip to content

'Beta' tag in UI for new teams and projects #6010

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

Closed
jldec opened this issue Oct 4, 2021 · 9 comments · Fixed by #6430
Closed

'Beta' tag in UI for new teams and projects #6010

jldec opened this issue Oct 4, 2021 · 9 comments · Fixed by #6430
Assignees
Labels
component: dashboard deployed Change is completely running in production feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. team: webapp Issue belongs to the WebApp team user experience

Comments

@jldec
Copy link
Contributor

jldec commented Oct 4, 2021

As a user discovering the new teams and projects capabilities, it would be good to know that the UI for this is still evolving.

The notification does not need to jarringly obvious, just clear enough for someone who is paying attention.

Extra: offering an easy link to the best place to provide feedback would also be nice.

@jldec jldec added user experience feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. team: webapp Issue belongs to the WebApp team labels Oct 4, 2021
@gtsiolis
Copy link
Contributor

gtsiolis commented Oct 11, 2021

Sharing some early drafts on how this could look like re-using the label component we've used in the What's New modal back in #4607. See relevant specs.

Things to consider:

  1. Using BETA instead of PREVIEW.
  2. Append a footnote in header, team creation, and project creation to make it visible is all possible steps.
  3. Adding the label on the header could require us to re-use the label in mumltiple pages like Prebuilds, Branches, and Prebuild.
  4. Team creation designs use designs from Update team creation designs #4951.
  5. We could also include a link to send feedback and link to Feedback Issue: Teams & Projects 💬 #5095.
Header New Team New Project
Header NewTeam NewProject

@0Grit
Copy link

0Grit commented Oct 12, 2021

Not going to lie, it was jarring.

@0Grit
Copy link

0Grit commented Oct 12, 2021

And I immediately gave the feedback to my team and I think on the gitpod discord that "The UX needs work"

Once I oriented myself, took some time, I realized I'd never go back.

@jldec
Copy link
Contributor Author

jldec commented Oct 13, 2021

This looks great @gtsiolis

  • I think I prefer Beta -- it's less easily confused as a verb / CTA.
  • I like the footers with the link to the feedback issue on the new Team and new Project steps
  • I think the footer does the job without introducing too much noise - no need for an additional header label.

@jldec
Copy link
Contributor Author

jldec commented Oct 13, 2021

/schedule

@jldec
Copy link
Contributor Author

jldec commented Oct 14, 2021

/assign

@jldec
Copy link
Contributor Author

jldec commented Oct 15, 2021

Regarding Beta vs Preview I think In Preview may be the better choice because it avoids the confusion of Preview being read as an action / verb and clicked on like a button.

That said, some people may interpret both Preview and In Preview as something that they can opt into (or turn off) somehow.

@JanKoehnlein
Copy link
Contributor

@jldec Do we still want to do this given that the feature is in the wild already and one is becoming the loading page for new users?

@jldec
Copy link
Contributor Author

jldec commented Oct 27, 2021

@JanKoehnlein I do think the low-key Beta notice sends a positive signal, even for new users.
Happy to take additional feedback.

Please see #6430 for screenshots
🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: dashboard deployed Change is completely running in production feature: teams and projects [DEPRECATED] Please, use feature: organizations or feature: projects labels instead. team: webapp Issue belongs to the WebApp team user experience
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants