Translate documentation to other languages

[Sogl]

Hello!

Some people with me want to translate Grav-learn to our native language. Where we can start? We can clone repo and do our job in a new branch, but what about multilang support in main learn site?

I talked with @flaviocopes in Slack and he suggested that I create an issue here.

[flaviocopes]

Some of my thoughts:

• Would be great to have translations for some sections (installation, introductory topics)
• We'd need to update a doc in multiple locations if we update something
• There is the risk a translation will be left idle with not updated content, with the risk of giving wrong/outdated instructions, because not knowning the language we can't update it, where it's not obvious (not in code snippets).

[Sogl]

@rhukster What do you think?

We started our work here in rus branch: https://github.com/zikkuratvk/grav-learn

I found some problems with existing learn site: 1.. Font-family (Work Sans etc) looks bad in Russian text. Normal font looks like bold especially with English words near of them:

2.. Tooltips in CSS. Not good thing for multilanguage:

I mean:

blockquote > blockquote > blockquote > blockquote > p:first-child:after {
      content: 'Warning'; }

[Sogl]

@w00fz @OleVik No plans for this thing in near future?

[OleVik]

I think Flavio's concerns are valid: The docs are written in an idiomatic tone, and frequently updated to reflect changes in methodology or thinking. Maintaining a language-specific fork of this would rely on an as active community within that language domain maintaining an up to date copy of the docs, which in itself is not a problem as this could be ran separately from the main docs. However, co-hosting the docs as multilanguage would require near 1:1 compatibility with the English docs.

Maintaining the docs in the same manner on the learn.getgrav.site would require a language-moderator for each additional language, that could review each PR specific to that language. Whilst not unthinkable, this would introduce a heavy overhead in managing translators as well as organization to have a repo or branch per language to pull from when updating the docs. Currently, this is a low overhead as the core devs can review and accept PRs that are automatically pushed to the live site.

[grav-it]

Having thought about a german translation.

Some other docs solve these kind of issues with an info box if a translated version is out of date.

Just brainstorming.