Use an i18n tool to maintain translations

[Hunter]

Originated from #153 (comment)

• Use jekyll-multiple-languages-plugin to maintain translations

@akz92 -- please coordinate with @benoittgt, as he will be moving the translated pages to the new layout.

[Lucas Moulin]

@onebree ok, I'll start this task tonight.
@benoittgt I believe it's better to wait for the i18n translation before moving the pages to the new layout, because once the translation is finished there will be only one page to move.

[Vinicius Torves]

Hi, @akz92
I can help with translations?

[Benoit Tigeot]

Ok @akz92 !

[Lucas Moulin]

Sure @vtorves. I'm still looking for the best approach, apparently i18n translation in Jekyll isn't as simple as it's in Rails. Maybe you could help me find good active gems to use or some examples/documentations.

[Vinicius Torves]

@akz92 rails really is very simple! I solved the translation using https://github.com/untra/polyglot .
how you prefer that i share my tests? branch? gist? here?

[Lucas Moulin]

@vtorves please commit it to a new brach.

[Hunter]

@vtorves as mentioned above, for any contributions, please do the following:

1. Fork this repository and fetch all branches
2. Checkout gh-pages then git checkout -b name-of-feature

[Lucas Moulin]

@vtorves can you share what you did? I didn't have the time to study other solutions, it would be great to see how you solved it.

[Vinicius Torves]

@onebree thanks!! =)
@akz92 of course ! yes I can. I will adjust better the flow and charge here tomorrow.