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
When signing up for a new account on the p5.js web editor, right now the only way to sign up is by entering in your email and username manually. This is pictured below:
However, when logging in, the log in page contains ways to log in through social accounts like Github and Google. This is pictured below:
I think, in terms of UX, it would be useful to include the option to sign up through social accounts on the sign up page, instead of it being located just on the log in page.
Thank you for considering this feature request!
The text was updated successfully, but these errors were encountered:
Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, be sure to follow the issue template if you haven't already.
Thanks for the feature suggestion! The underlying technology already works, to sign up with GitHub or Google, it's just a matter of putting those buttons on the sign up page 😸
I am new to contributing to open source projects. As a coincidence when I was looking through the user interface I started thinking of the same idea as presented in this issue. Therefore, I am interested in working on this issue, is that OK?
hmaddisb
added a commit
to hmaddisb/p5.js-web-editor
that referenced
this issue
May 18, 2020
Nature of issue?
New feature details:
When signing up for a new account on the p5.js web editor, right now the only way to sign up is by entering in your email and username manually. This is pictured below:
However, when logging in, the log in page contains ways to log in through social accounts like Github and Google. This is pictured below:
I think, in terms of UX, it would be useful to include the option to sign up through social accounts on the sign up page, instead of it being located just on the log in page.
Thank you for considering this feature request!
The text was updated successfully, but these errors were encountered: