Repos are forked under clojurebridgeBA already: https://github.com/ClojureBridgeBA/welcometoclojurebridge, https://github.com/ClojureBridgeBA/drawing, etc.

Example of files that would need translation are https://github.com/ClojureBridgeBA/welcometoclojurebridge/blob/master/README.md, https://github.com/ClojureBridgeBA/welcometoclojurebridge/blob/master/outline/TURTLE.md, https://github.com/ClojureBridgeBA/welcometoclojurebridge/blob/master/outline/TURTLE-SAMPLES.md, etc.

This file outline/simple_values.md

This is the file: https://github.com/ClojureBridgeBA/drawing/blob/master/curriculum/first-program.md

This file https://github.com/ClojureBridgeBA/curriculum/blob/gh-pages/outline/setup_ubuntu.md

Those files gh-pages/outline/cheatsheet-quil.md
gh-pages/outline/cheatsheet.md

The files are setup_win7.md and setup_win8.md. Maybe we don't need both, and we could just even do es/outline/setup_win10.md. Or we could not specify the version even thought we would use a specific version...

Anyways, it would be really nice to have a translated version of the setup for windows :)

Translate this file outline/data_structures.md and place them in /es directory.

We started working off the gh-pages-es branch instead of gh-pages with the idea of sending a PR to the upstream repository in the near future, and once that PR got merged we would switch back to gh-pages. But the problem with not using gh-pages now is that we cannot publish the slides in https://clojurebridgeba.github.io/curriculum/es, because Github Pages only allows to publish your page from the gh-pages or from the master branch (sighhh).

We should switch back to gh-pages ASAP, updating the existing PRs to have gh-pages as its base. If and when our translation makes it to the upstream repo, we would merge with its gh-pages branch, there shouldn't be any conflicts anyways.

This file https://github.com/ClojureBridgeBA/curriculum/blob/gh-pages/outline/setup_osx.md