@indexzero, @mmalecki, @jvduf
Review and merge. Also included example
OK, I'll strip out the builds and put them in gh-pages as discussed. Please stand by as git magic happens.
@indexzero Can you enable GitHub pages for this project? We came up with an idea that we shouldn't put our output files in master but make a gh-pages branch and put them in there with some simple download page (also, easier hotlinking).
@mmalecki, you should do it for director too.
@pksunkara @mmalecki Created
@mmalecki gh-pages are active, can you throw in the builds?
@indexzero can you merge to master?
@jvduf Yeah, I'm on it. I'll force-push frontend branch to strip output files first.
@mmalecki Include the build/* files as browser programmers may not have node installed to build them. We include them in director as well.
@indexzero They will be included in gh-pages. Programmers will be able to download them from the GitHub page (http://flatiron.github.com/broadway).
Also, GitHub uses CDN for that, so it's going to be easier to hotlink.
[api] Codesurgeon build for browser
Win! I'll put these builds in gh-pages now.