this is github pages. it is neither new nor unknown. move along please.<p>first four paragraphs are a personal anecdote, and the last 2 are a regurgitation of the official github pages documentation, which the author links to.
This will effectively limit you to making requests to services that provide an API that supports JSONP. If you're going to do something like this, why not just use Heroku or something similar? Unless you're relying solely on external APIs, you're going to need some server space sooner or later.<p>Github is good for static pages, like blogs, but I don't think a web application will work that well.
I have a side project where I want to figure out how to host a database on github. If there was a javascript API for doing git business on github, then could just update the database to and fro. It would be messy of course but it wouldn't matter. Because you would have a dynamic app up on github for free (or 7/month if you wanted your secret sauce to stay secret).
I moved my blog to it some time ago and it's been excellent so far. I do kind of think this is out of scope for GitHub, and will probably move to S3 at some point.<p>I did switch from Jekyll to Octopress though (Octopress is a nice framework around Jekyll that automates the annoying manual bits involved with Jekyll). So far it's been great though!
If you have written a JavaScript library and it's hosted on GitHub, I wonder if you can somehow include the `master` branch in your `gh-pages` branch as a submodule. Do you get me? If the core repo is clean JS, but where your demo site might want to include that JS, plus some extra pages.
You cannot access any arbitary website from Javascript.
<a href="http://en.wikipedia.org/wiki/Same_origin_policy" rel="nofollow">http://en.wikipedia.org/wiki/Same_origin_policy</a>