Svelte: add welcome introduction when enabling svelte for the first time#64163
Svelte: add welcome introduction when enabling svelte for the first time#64163camdencheek merged 21 commits intomainfrom
Conversation
d3db2d5 to
38a34d1
Compare
There was a problem hiding this comment.
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.
Let's use the forum: https://community.sourcegraph.com/c/code-search/9 |
Sounds good to me. I assume we do not want to show it to users for which it's on by default?
I added that after taking the video (it's in the screenshots). My bad 😅
Oops, yep. Forgot that in the "followups" section. Implementation is surprisingly tricky on that one
Whoops, will adjust before merge.
That only exists in local dev. Customers should never see that. Note I removed it when I took the screenshots because it's distracting 🙂 |
We can, but just the first time. So everyone gets to see it once at least.
Sweet! |
bahrmichael
left a comment
There was a problem hiding this comment.
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.
|
|
||
| 'webNext.welcomeOverlay.dismissed': boolean | ||
| 'webNext.departureMessage.dismissed': boolean | ||
| 'webNext.toggled.on': boolean // whether the user has explicitly enabled with the toggle |
There was a problem hiding this comment.
Can we not turn webNext.toggled.on and webNext.toggled.on into a single setting? By default, undefined means not set.
There was a problem hiding this comment.
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
|
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. |
PR is updated with this behavior now btw |
peterguy
left a comment
There was a problem hiding this comment.
Lots of comments and suggestions; nothing blocking. Approving to unblock merging.
This implements a welcome dialog and some additional messaging around the beta rollout.
Walkthrough video of the behavior
Figma design
Followups:
Test plan
Manually tested the onboarding flow.