Can we move the whole HTML build process to Travis

[annevk]

I've lost track a bit about how the various pieces fit together, but it seems whatwg/html already uses Travis to build the HTML Standard. Why not add some rsync/scp at the end of that and remove all scripts from the server? Having the server just host static resources seems much better.

[domenic]

That's probably doable.

Currently Travis is only used as a validation step. It uses wattsi-server. Whereas, the build on the actual server uses a local copy of Wattsi.

Given that we already use Bikeshed via its web service I guess there's no problem with relying on wattsi-server.