We at OpenTechSchool Berlin like and have used this workshop a lot in the past. As part of our efforts to make our events more inclusive, we'd like to translate it into other Languages so as to provide an entry to programming for people not entirely fluent in the English language.

We also have a Git workshop, in which we have participants make PRs to a not-so-useful repo.

With @bastianalbers we're contemplating running a Git workshop in which we ask participants to create PRs for translating the CSS classes.

Now, there's a range of technical options for including translations on Jekyll pages:

We could use Sphinx, which would require all content to be converted to reStructuredText, but would allow the repo to be translated using Transifex, which is much easier to use for non-Coders in the future.

Another good option would be using https://github.com/screeninteraction/jekyll-multiple-languages-plugin to translate stuff. It fits in better with the Ruby/Rails way of doing things (.yml files instead of .po files for translations, markdown support).

I don't have a strong opinion on using either of these options or even a third one, as long as it allows

• Interaction with the repository using git
• All translations are kept in the master branch (and ideally synchronized so there's a way of knowing whether a translation is out of date).

What do you think? I'd be happy to provide a PR that prepares the repo for being translated.