Skip to content

feat: move workspace name in post-pro flow #8062

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

Merged
merged 4 commits into from
Sep 11, 2023
Merged

Conversation

alexnm
Copy link
Contributor

@alexnm alexnm commented Sep 8, 2023

Closes PC-1222

Removes the step to name the workspace / create team before going to stripe.

On the pro page, when you start trial / upgrade to pro you go directly to stripe
When stripe redirects to the dashboard, you end up with new_workspace=true in the query string.
The modal window now has 3 steps:
image
image
image

A few style adjustments to match on all 3 screens

@alexnm alexnm requested review from danilowoz and necoline September 8, 2023 14:50
@codesandbox
Copy link

codesandbox bot commented Sep 8, 2023

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@linear
Copy link

linear bot commented Sep 8, 2023

PC-1222 Remove first step to add team name

The problem

We are learning that users are deterred by naming their workspace, they expect to go straight to stripe

(see parent ticket)

I think we should look into removing the step where we have users name their workspace before creating a subscription. I know that we implemented this step bc the BE needs a team name to attach to a subscription.

alex sanne can we do this behind the scenes? I'm not sure if the client should pass in a filler team name or if the BE could do it, but I'm thinking that the steps would be

  • from /pro users select Upgrade to pro
  • either the client names the team something generic like [username]'s pro and send that through on behalf of the user or the BE does something similar
  • user fills in strip details
  • we show a welcome screen where the user can name their workspace and invite others to join
  • in the future we could have an option for them to move their sandboxes from their personal to the new workspace
  • direct users to the workspace onboarding screen

Copy link
Contributor

@necoline necoline left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love the styling changes!

@codesandbox-ci
Copy link

codesandbox-ci bot commented Sep 8, 2023

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 40093f7:

Sandbox Source
Notifications Test Configuration

@necoline necoline merged commit dd9876a into master Sep 11, 2023
@necoline necoline deleted the draft/purple-moon branch September 11, 2023 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants