Redirect new users to /new

[gtsiolis]

Problem to solve

In the upcoming Teams & Projects feature, we'd like to also introduce an onboarding flow that helps users get a well-configured, prebuilt, ready-to-code dev environment for their project. See also https://github.com/gitpod-io/roadmap/issues/8. 🗺️

Back in #4443, we've added the first bits of this new onboarding flow (/new) but this is still not enabled for new users signing up.

Proposal

Let's redirect all new users to /new.

Note The simplest strategy to do this would be (A) to change the 'Try Now' CTA link from the website. An alternative strategy (B) would be to auto-detect new users inside the dashboard by distinguishing logins from signups, and then redirecting signups to /new.

Depends on

(JL) Moving forward with this depends minimally on:

• Enable "New Workspace" button in Project Configuration without first having to use "Run Prebuild" button #6303
• 'Beta' tag in UI for new teams and projects #6010 also has a link to open a workspace with an example repo (screenshots in PR)
• New Project flow fails detection on private repos if oauth is fresh #6168

Once ☝️ are deployed, ship change to website 👇

• gitpod-io/website#1139

Addendum

While waiting for #5583

• gitpod-io/website#1194

[mteam88]

I think this is a good idea.

[JanKoehnlein]

/schedule

[roboquat]

@JanKoehnlein: Issue scheduled in the meta team (WIP: 0)

In response to this:

/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jldec]

Notes from design discussion with @gtsiolis 🙏

• This applies to users who sign up via a the website (Sign Up or Try Now CTA)

• Instead of an intermediate webiste page, visitors will go straight to https://gitpod.io/new in the dashboard.

• This starts a New Project flow which (assuming user is unauthenticted) would begin with the git provider Log in to Gitpod page (1st screenshot below), but could potentially be adjusted to announce itself as New Project (similar to the 2nd screenshot below).

• After authenticating the steps depend on whether it's GitHub (to install the Gitpod App) or GitLab (which uses api scope)

• Finally a repo is selected and optionally a new team is created to hold the new Project.

---

[jldec]

A previewable website PR from gitpod-io/website#1140 with adjusted CTA flow to dashboard /new is now available at
https://deploy-preview-1140--gitpod-kumquat.netlify.app/

[jldec]

@gtsiolis - I added an alternative strategy (B) for how to do this to the original post above. Is that how were thinking it would work, when you first wrote the issue?

[gtsiolis]

@jldec yes, the initial goal of this issue was to propose redirecting to /new only users that create an account with Gitpod. Users with already an account would be redirected to / which redirects to /projects as usual.

However, there's a separate issue where we could visually distinguish sign in and sign up pages and flows. See also relevant comment in #5975 (comment).

[jldec]

Thanks @gtsiolis - I like the suggestion to handle the signup/login visual distinction separately in #5975

For this issue, let's proceed with changing the onboarding "Try Now" CTA on the website as a first step.
i.e. move forward with https://github.com/gitpod-io/website/issues/1139 and the PR https://github.com/gitpod-io/website/pull/1140

This will accomplish:

1. users not having to select a git provider twice (once on the website and once on the dashboard signup), and
2. reduce the number of steps right after dashboard signup to go straight into the new project flow.