Internationalization about dcrdocs HOT 8 CLOSED

Would love comments on this from @dajohi, @jolan, @karamble, @gratefulcheddar, and anyone else interested.

from dcrdocs.

I agree. I have researched on the multilanguage issue on mkdocs and couldn't find a reliable solution. My first thought was the same, having multiple directories for the various languages including the full set of docs. We should keep the filenames of the .md files consistent over the language directories so it would be easier to track if the subpages are allready translated.

We also need a mkdocs.yml for each language. en_mkdocs.yml is my suggestion.

Also to make the work for the admin easier we can add a build-the-docs.sh bash script that handles the build process, renaming directories etc. So the admin would just need to point the virtualhosts of the subdomains to the specific language directories.

I will start translating into german and try to prepare the directory structure and the build bash script just to get a feeling for it, as i have only used the 'serve' function instead of building the docs yet.

from dcrdocs.

@karamble so sounds like you are in favor of option 2 above.

Anyone else want to chime in?

from dcrdocs.

I've looked at hugo a bit which seems suitable as a mkdocs replacement. They have a few ways of doing internationalization:

https://gohugo.io/content/multilingual/

I'm not sure it's really worth the effort to switch over since it would require porting the template to be hugo-compatible, having everyone learn golang template syntax, etc.

I am fine with what @karamble proposes. If we hit snags with that method then we can consider switching.

from dcrdocs.

I agree with @jolan. Was gonna throw Hugo out there as a suggestion but the work required to switch may not be worth it.

from dcrdocs.

I am fine with option 2. I strongly support subdirs over subdomains.

from dcrdocs.

Some experiments/initial work on this by @karamble are in #96

from dcrdocs.

This was done in #96

from dcrdocs.