generated from json-schema-org/repo-template
-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Improve the churn rate of the tour #72
Labels
✨ Enhancement
New feature or request
Priority: High
After critical issues are fixed, these should be dealt with before any further issues.
Comments
JeelRajodiya
added
Priority: High
After critical issues are fixed, these should be dealt with before any further issues.
✨ Enhancement
New feature or request
labels
Aug 23, 2024
One Observation:
Possible Causes:
|
JeelRajodiya
added a commit
that referenced
this issue
Sep 6, 2024
There was no improvement in the churn rate related to #72
hi @JeelRajodiya , can I be assigned this issue. would like to analyze and come up with a solution |
Hello @AkshataABhat, Thanks for your interest. However, I am currently working on the issue. We are experimenting with the project. If you wish to contribute, issues #53 and #10 are a good start! You can start from one of them. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
✨ Enhancement
New feature or request
Priority: High
After critical issues are fixed, these should be dealt with before any further issues.
Based on the analytics, we've observed that around 39% of users proceed beyond the first lesson. We want to improve this rate.
Possible Causes:
Possible Solutions:
The Tour is for developers with 0 experience in JSON Schema and probably most of them have experience on it. If that is true we can add small survey in the beginning to better understand the user experience and suggest them start in advanced sections.Give direct links to the chapters in the landing pageThe text was updated successfully, but these errors were encountered: