I'm pushing forward how I'm using Github to build prototypes and even full blown applications. I've been publishing all of my public sites using Github + Github Pages for most of the year, but this last week I've taken my usage of Github to new levels.
- oAuth.io - Simple API integration for Github and other providers
Using oAuth.io I'm able to provide a logon via Github, that is entirely client-side on Github Pages. So there is no server side handling of the oAuth flow(by me), allowing me to authenticate users via Github Pages, securing content behind it in a private repo or allow for editing and saving of content and data live from Github once a user is authenticated.
This is a quick and dirty way to allow a user to manage content via pages and data via JSON using a custom interface I've built and running via Github pages, with no server side technology needed--Github does all of the heavy lifting.
I'm in the early days of building applications via Github in this way, so I'm sure I will get more sophisticated in my approach in the coming months. oAuth.io and Github.js has allowed me to move into this new realm and overcome some pretty significant hurdles in how I secure my applications and provide a backend for them that runs exclusively on Github.