Consider Webby and Jekyll as descendents of a common ancestor idea. They share many things in common but are adapting to different needs. Most importantly, because Jekyll is restricted to Liquid for scriptability, it is safe to run server-side. Jekyll also processes non-Jekyll (plain HTML) sites unchanged, whereas Webby refuses to run at all without a config file. Jekyll also relies more heavily on conventions to reduce the organizational overhead of the maintainer. Webby is a great system, and I'd like to pull over some features from it, but I will do so under the philosophy and adaptations of Jekyll. Besides, if you like how Webby works, then you can use it to generate a site and push that to GitHub, just like Webby intends for you to do!