Create a "Translation Guide" on the docs

[Mariatta]

Thanks to the work of @jtemporal and @cecivieira for setting up the project for translations along with the documentation.

Currently the translation docs is written under "Developers Guide > Howto". Perhaps we could have a new section on the doc, eg in the same level as Developer Guide, User Guide, and then we add one more "Translations Guide".

Within the TRanslatins Guide we can add a differnet sections like:

• How to translate, how to add a new language
• Current available translations
• etc?

[Mariatta]

Is this something we can do as part of the CI, to check that text have translations or not? Do we need to add anything to GitHub Actions or deployment?

[jtemporal]

I actually started working on the commands for the makefile yesterday and I do believe we should at least add the "compilemessages" to the CI. But our image doesn't have the GNU gettext that is required for the translations commands so I tried adding it but got stuck, I'll try again later today and share if I get it to work.

On the adding translations sections to the user guide I agree that could be a good thing maybe we can link out to the howtos in order to avoid duplicated content and work 🤔

[jtemporal]

Okay, took me a while but I put through #163 some notes:

• The library gettext is now available on the docker image and we shouldn't have issues using it for translations anymore 🎉
• I believe we should add the compile_translations to the deployment step, this will guarantee that translations will be visible, adding it to the CI could be interesting for translation preview on netlify but is not mandatory in my opinion
• In the localized projects I worked in the past we used to avoid committing the .mo files to have less things to track as the compilation was done while deploying. While thinking about this: if we add the compile step to the deployment and the CI we wouldn't need to commit compilation files to the repo but I believe this is more of a choice we can make if we want to.