There's also support in http://agaveapi.co for running any Docker image anywhere.

Another project called End of Day (https://github.com/joestubbs/endofday) is akin to Rabix. It allows you to build and share pipelines defined as a YAML file. EoD can run Docker containers locally or in the cloud. It also supports mixing and matching local/remote execution so you can swap out your own versions of steps in the pipeline to experiment. All data management and rovenance is handled for you.

It doesn't get much easier than markdown to author and git push to commit. The value of this over a wiki is that you can actually tell when content changed by looking at the commit log. As a bonus, we get a gitter channel to accompany the site and provide archived conversation.
See the last point on hosting.

I’m not dogmatic about the blog/website builder we use, but may I recommend that if we’re going to push everything to github, that we use github static hosting to host the website off a branch of the project repo. That lets us track changes, consolidate contributions, and streamlines questions about how to contribute.

If it helps, Agave has a transform service that can handle some basic transformations for you. it can also provide hosting and public URLs that people can pull down over the web or request scheduled reliable transfer offline. May be easier than forcing people to pull down a repo of data they may not want.