You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, many thanks to all contributors for their amazing work on JSON Schema! 💯
It was an absolute pleasure to dive into the tour and learn about JSON Schema in depth.
Unfortunately, I encountered an issue when trying to obtain my certificate after completing the tour. I did not receive any email, not even a confirmation, which left me uncertain about the status of my request.
After reviewing the code, I noticed that clicking the Get Your Certificate button triggers an HTTP request to a Google Doc, but it seems there’s a gap in the process.
Suggestions for Improvement:
To improve the user experience and make the certificate process more robust, here are a few suggestions:
Send a Confirmation Email:
When a user clicks the Get Your Certificate button, send a confirmation email to inform them that their request has been received and that they have been added to the list.
Integrate with LinkedIn:
Provide users with the option to add the certificate directly to their LinkedIn profiles. This would greatly enhance the value and visibility of the achievement.
Use GitHub Profile Instead of Email:
For authentication and certificate delivery, consider using GitHub profiles instead of emails. This approach could streamline the process, as GitHub authentication is already widely used by developers and could reduce reliance on email communication.
Thank you for considering these suggestions. I’d be happy to provide further feedback or assist with testing improvements to this process.
The text was updated successfully, but these errors were encountered:
First of all, many thanks to all contributors for their amazing work on JSON Schema! 💯
It was an absolute pleasure to dive into the tour and learn about JSON Schema in depth.
Unfortunately, I encountered an issue when trying to obtain my certificate after completing the tour. I did not receive any email, not even a confirmation, which left me uncertain about the status of my request.
After reviewing the code, I noticed that clicking the Get Your Certificate button triggers an HTTP request to a Google Doc, but it seems there’s a gap in the process.
Suggestions for Improvement:
To improve the user experience and make the certificate process more robust, here are a few suggestions:
Send a Confirmation Email:
When a user clicks the Get Your Certificate button, send a confirmation email to inform them that their request has been received and that they have been added to the list.
Integrate with LinkedIn:
Provide users with the option to add the certificate directly to their LinkedIn profiles. This would greatly enhance the value and visibility of the achievement.
Use GitHub Profile Instead of Email:
For authentication and certificate delivery, consider using GitHub profiles instead of emails. This approach could streamline the process, as GitHub authentication is already widely used by developers and could reduce reliance on email communication.
Thank you for considering these suggestions. I’d be happy to provide further feedback or assist with testing improvements to this process.
The text was updated successfully, but these errors were encountered: