-
Notifications
You must be signed in to change notification settings - Fork 36
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
feat(studio): adds guided tour button to top #227
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small comment otherwise LGTM! Nice work!
if (analytics) { | ||
// analytics only defined if window.SEND_USAGE_STATS is true | ||
return analytics.track(eventName, payload, options, callback) | ||
analytics.track(eventName, payload, options, callback).catch(e => { | ||
console.error('Analytics error - event', e) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really want to log those errors? I don't think it has much value to let the user know that sending analytics failed. What do you think?
@ptrckbp Any update? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Running a little experiment to see if people want to use the tutorial / help buttons in app. On pages with no help icon (like the flow editor), a tutorial button appears (see images), where the help button would normally be and triggers the Guided Tour.
This also standardizes the buttons to have the same spacing, and icon + title.
On a page with no existing help button :
Before
After
On a page with an existing help button :
Before
After
This also adds analytics to the tutorial steps and simplifies the tracking implementation by removing error handling.