Just something you should have in mind: gh-pages are limited in size.
I've been thinking doing an experimental application using gh-pages as storage layer for some time now. Like you, the authentication became an issue.
One solution I found though is to force your users to connect by providing a GH token (rather than some email password) that would be stored as cookie 🍪 in their browser (don't save it anywhere else!).
After, to alter the state of your application, you should commit changes using their token. But yeah, any data will be public.
Just something you should have in mind: gh-pages are limited in size.
I've been thinking doing an experimental application using gh-pages as storage layer for some time now. Like you, the authentication became an issue.
One solution I found though is to force your users to connect by providing a GH token (rather than some email password) that would be stored as cookie 🍪 in their browser (don't save it anywhere else!).
After, to alter the state of your application, you should commit changes using their token. But yeah, any data will be public.
Hope that helps
I also just found out that you can use firebase.google.com as for authentication. It worked quite well!