What about translations of your curriculum

1. In the dev world, most is English. It's almost required to know English to develop software

2. We would not be able to maintain a spoken language that we, ourselves, do not know

3. The external resources which we use a LOT of, would have to be translated as well, this means contacting ALL the authors and getting permission to do so. If we get turned down, one would then need to write, or find an equivalent resource to fill the spot.

4. The course would be impossible to keep updated on the translated version, people make changes daily on the site, and most people only know English. It would require a full-time job to keep up with those changes and making sure that parity stays the same. If there's an incorrect statement, it may go un-noticed in one language

5. It would require an entirely different community, it would be a disservice to both spoken languages to put them into the same bucket. TOP is mostly defined by the community here, and the non English community would need to be grown from the ground up.

6. The TOP team does not have the resources to manage another spoken language.

Though, you may do this:

• Take the content and modify it according to the license, this means you can translate TOP, but you must keep it free and never make money from the content.
• Fork the site, rebrand, and host a translated version on your own domain, though the translated texts must continue to be free

Please review our curriculum's license for more details