When you're using English every day to read, write, and even code, it can be easy to forget that a big majority of the planet's population doesn't speak the language.

The truth is that language barrier is a very real problem, and it's the reason why we want to make Discover Meteor available in as many languages as we can. But Discover Meteor being a self-published book, we don't have the resources to hire translators and editors for every single language.

The Discover Meteor Translation Project

So we need your help: by helping us translate the book in your own language, you'll be helping more people around the world learn Meteor, adding value to the whole Meteor ecosystem, and fostering the Meteor community in your language.

But we don't think it would be fair for us to make money off your hard work. This is why every translation of Discover Meteor will be available for free to everybody (whether or not they've bought the English version of the book), licensed under a Creative Commons Attribution-NonCommercial license.

Getting Started

Contributing To An Existing Language

  • Ask to join the GitHub team for a language by posting an issue in its repository on GitHub and mentioning @SachaG in the issue's body. Being part of the team will give you access to the English sources in Markdown format and let you push to the repository.

Starting A New Language

  • Get in touch if you'd like to start a new repo, making sure to mention your GitHub username and the language you'd like to help with. Just give us a little bit of time to set up the new repo and site, and you'll be ready to go!

Translation Guidelines

  • Do not modify the YAML frontmatter at the top of each chapter, except for the title and contents fields.
  • Each new translation starts off from the outline of the book. Note that the outline is provided as more of a general guideline, and may not always be up to date with the source English version.
  • Please use the English version repository as a source for your translation, as it's always going to be the most up-to-date version of the book.
  • If you'd like to preview translations locally, check out the Discover Meteor Static app.
  • Open a new issue in your language's GitHub repo when you start working on a new chapter.
  • If you're translating into a new language, you might also want to translate the project's user interface strings.
  • Translating the Vocabulary chapter first can be a good way to get everybody on the same page and using the same terms.
  • Try to commit and push to GitHub frequently as you translate, and make sure you also pull the latest version of the translation regularly to avoid duplicating work.
  • Check translation percentages for each chapter on the translation's site to see what remains to be done.
  • Try to remain as close to the original text as possible in terms of layout and formatting.
  • That being said, feel free to adapt the text so that the end result feels natural in your language.
  • You might want to create (or contribute to) a COMMON.md file that tracks common expressions to make sure they're translated in a consistent way throughout the book.
  • Don't forget you can also edit files right on GitHub if you need to.
  • If you have any questions, come chat with us in the Discover Meteor chatroom.
  • Please only translate content provided in the English version repository (i.e. not the extra chapters).
  • When updating a translation, a good way to see all changes since a previous commmit is to diff that previous commit with the master version. Just replace the commit's hash in the URL with the hash of the last translated commit.