Hi team,
I noticed an effort were done regarding non french contributors, this is really nice and welcome! Thank you!
Kind request n°1: please do not use flags for languages
- I opened a Pull Request to remove flags from Docs: Remove flags (!10) · Requêtes de fusion · Panoramax / Panoramax - Main documentation · GitLab
- I don’t have the skills for the website, but it is the same subject: translation / please replace flags by local language names (#16) · Issues · Panoramax / Server / Panoramax.fr Website · GitLab
I see docs . panoramax . fr is build using mkdocs.
It looks like to be the aggregation of documentation coming from multiple repositories?
I do know how to automate static website localization.
I know how to do it with gohugo + scripts_with_po4a + weblate
While I have nothing agains mkdocs, I don’t really understand the value of this tool here.
Would it be valuable for you to have all docs in the same place and have the automation with weblate and automation for publication?
I created a proof of concept here: languages-in-floss . eu/fr/2020/07/comment-contribuer-%C3%A0-la-traduction-de-la-distribution-linux-fedora/
You can see you can jump from one language to the next really easily, with lot of good feature (translated URL, internal links works, etc.)
All is automated for publication: github . com/languages-in-floss/site/commits/master/
I can do this for Panoramax project if you feel like it.
Requirements would be to move documentation content in one single repository.
To use gohugo instead of mkdocs (content can be written in markdown, no problem here)
I can do most of it myself if you provide guidance/support on where is the content.
I’ll provide automation scripts and can do Weblate configuration.
I’ll need your help on the template html/css.
If this works fine for documentation, you may want to reuse same behavior for other content, you’ll tell me. Let’s start little.
(sorry for the links, the forum prevents to have more than two URLs for new user…)