Skip to content
This repository was archived by the owner on Sep 30, 2024. It is now read-only.

Svelte: add welcome introduction when enabling svelte for the first time#64163

Merged
camdencheek merged 21 commits intomainfrom
cc/activate-cta
Aug 1, 2024
Merged

Svelte: add welcome introduction when enabling svelte for the first time#64163
camdencheek merged 21 commits intomainfrom
cc/activate-cta

Conversation

@camdencheek
Copy link
Member

@camdencheek camdencheek commented Jul 30, 2024

This implements a welcome dialog and some additional messaging around the beta rollout.

screenshot-2024-07-30_18-04-26@2x

screenshot-2024-07-30_18-03-13@2x

screenshot-2024-07-30_18-06-58@2x

screenshot-2024-07-30_18-09-29@2x

Walkthrough video of the behavior

Figma design

Followups:

  • Work on in-app feeback form (SRCH-823)
  • Insert release notes link
  • Add a nudge towards the feedback button when activated

Test plan

Manually tested the onboarding flow.

@cla-bot cla-bot bot added the cla-signed label Jul 30, 2024
@camdencheek camdencheek changed the title Cc/activate cta Svelte: add welcome introduction when enabling svelte for the first time Jul 30, 2024
@camdencheek camdencheek marked this pull request as ready for review July 30, 2024 23:27
@camdencheek camdencheek requested review from a team and taiyab July 30, 2024 23:27
Copy link
Contributor

@taiyab taiyab left a comment

Choose a reason for hiding this comment

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

First off: incredible work @camdencheek, this is looking slick!

On review of everything, I think we can afford to, right now, actually show the intro modal every time someone reactivates the new experience. Because we're not expecting people to constantly move back and forth, the extra button click is a decent tradeoff for both the additional instruction/context and sense of confirmation the modal gives you.

A few little niggles:

  • we're missing the CMD+K badge next to the "reworked fuzzy finder" title (that's my bad, I didn't make sure it was in both light/dark designs)
  • we're missing a way to prep users to think about leaving us feedback on that modal state (although I'm assuming this could just be something you decided to skip for this minimal version, in which case, we can add a line of copy to the small subtext below the "Awesome, I'm ready to use it!" button telling users they can also leave feedback)
  • the modal backgrounds don't look like they match up with the designs
  • we could consider linking to the discord, although I suspect that's more for the PLG audience and would look pretty scrappy for enterprise folks (can you confirm this @jdorfman?)

Not directly related to this PR: would it be possible to rehouse the "developer settings" UI into the profile dropdown too, to ensure we don't have that taking up valuable header space, especially when we want the default React version to also use the minimal navigation? There also might be other states/things like that that clog up the header area that we might want to accommodate for.

EDIT: Although, thinking about the "Developer settings" thing a bit more, does it ever need to be accessible to non-authed users?

Overall, incredible stuff. All my feedback is non-blocking to merge this.

@taiyab taiyab requested a review from a team July 31, 2024 03:45
@jdorfman
Copy link
Member

@taiyab

we could consider linking to the discord, although I suspect that's more for the PLG audience and would look pretty scrappy for enterprise folks (can you confirm this @jdorfman?)

Let's use the forum: https://community.sourcegraph.com/c/code-search/9

@camdencheek
Copy link
Member Author

camdencheek commented Jul 31, 2024

I think we can afford to, right now, actually show the intro modal every time someone reactivates the new experience

Sounds good to me. I assume we do not want to show it to users for which it's on by default?

we're missing the CMD+K badge next to the "reworked fuzzy finder" title (that's my bad, I didn't make sure it was in both light/dark designs)

I added that after taking the video (it's in the screenshots). My bad 😅

we're missing a way to prep users to think about leaving us feedback on that modal state

Oops, yep. Forgot that in the "followups" section. Implementation is surprisingly tricky on that one

the modal backgrounds don't look like they match up with the designs

Whoops, will adjust before merge.

rehouse the "developer settings" UI

That only exists in local dev. Customers should never see that. Note I removed it when I took the screenshots because it's distracting 🙂

@taiyab
Copy link
Contributor

taiyab commented Jul 31, 2024

I think we can afford to, right now, actually show the intro modal every time someone reactivates the new experience

Sounds good to me. I assume we do not want to show it to users for which it's on by default?

We can, but just the first time. So everyone gets to see it once at least.

rehouse the "developer settings" UI

That only exists in local dev. Customers should never see that. Note I removed it when I took the screenshots because it's distracting 🙂

Sweet!

Copy link
Contributor

@bahrmichael bahrmichael left a comment

Choose a reason for hiding this comment

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

Code looks good to me. I'd like to see the "which IS now available in beta" fixed, but apart from that good to go.

@camdencheek camdencheek requested a review from bahrmichael July 31, 2024 14:02

'webNext.welcomeOverlay.dismissed': boolean
'webNext.departureMessage.dismissed': boolean
'webNext.toggled.on': boolean // whether the user has explicitly enabled with the toggle
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we not turn webNext.toggled.on and webNext.toggled.on into a single setting? By default, undefined means not set.

Copy link
Member Author

Choose a reason for hiding this comment

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

Hmm, you might be right. I think this behavior is going to change a bit based on Taiyab's feedback, but I'll take a look at consolidating

@rrhyne
Copy link
Contributor

rrhyne commented Jul 31, 2024

There is some valuable info here. What if below the description we offer a quick link to open the intro again?

@camdencheek camdencheek enabled auto-merge (squash) July 31, 2024 15:36
@taiyab
Copy link
Contributor

taiyab commented Jul 31, 2024

There is some valuable info here. What if below the description we offer a quick link to open the intro again?

Semi relevant to this: we're gonna show the modal every time you switch into the new experience (rather than once). Seeing as people are unlikely to be constantly switching back and forth, I thought the tradeoff was worth hitting an extra button each time to get that import primer info upfront each time.

@camdencheek camdencheek requested a review from a team July 31, 2024 15:46
@camdencheek
Copy link
Member Author

show the modal every time you switch into the new experience

PR is updated with this behavior now btw

Copy link
Contributor

@peterguy peterguy left a comment

Choose a reason for hiding this comment

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

Lots of comments and suggestions; nothing blocking. Approving to unblock merging.

@camdencheek camdencheek merged commit be17da7 into main Aug 1, 2024
@camdencheek camdencheek deleted the cc/activate-cta branch August 1, 2024 09:06
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants