Continuing from #9466.
@Hainish

As suggested, we should probably support the FAQ translation (as Privacy Badger does). Initially the translation process was there: EFForg/www-l10n, but this repo was not very active so we should consider making the translations in the https-everywhere repository.

We have two options:

1. Do all the job on GitHub through pull requests. In this case we should create a folder for each language inside the docs folder (docs/en_US, docs/fr, docs/it, ...) and just translate the .md files directly without changing the Markdown syntax. Here the problem is about the review of the translations (how can we assure the quality of the translations?).

2. Move the translation process to Transifex (EFF already as an account there). The problem in this case is about the creation of the .md files from the Transifex translation files. Also, it isn't very common to translate markdown files with Transifex. On the other side, Transifex offer a great platform for translator that will probably increase contributions.

What should we do? Do you have any other option?