Why don't you create a gh-pages branch ?

[rhulha]

It would look something like this:

http://rhulha.github.io/goojs/visual-test/goo/addons/ammopack/Ammo-vehicle-vtest.html

[hccampos]

That is a nice idea actually. @schteppe @rherlitz ?

[schteppe]

I'm not sure what it would add really. We already host the stuff on http://code.gooengine.com...?

[rhulha]

Having gh-pages as a branch of master serves multiple purposes:

• Easily prove to users that the code runs in a browser and the project is testable with almost zero effort
• Survive even if code.gooengine.com is down or unreachable
• gh-pages is free, now that Goo is open source, why not reap the benefits that GitHub provides ?
• Easy to update, just merge master into it again and push.
• Some users expect or at least appreciate a github.io presence
• It might add another input to Google.
• Even if you decide not to advertise it, why not do it ? Is there any bad side to having that branch ?

[hccampos]

I am with Ray on this one. We don't lose anything at all by having it. I guess maybe just the fact that we need to merge things into it on every release.

[rhulha]

To add to this: If you google for GooJS, the GitHub page is already the top result.
The code.gooengine.com page is not even on the page...

PS: The gh-pages for the learn project is the third result ;-)