Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What can we do to prepare the site for multiple languages? #225

Open
sr2ds opened this issue Apr 13, 2021 · 2 comments
Open

What can we do to prepare the site for multiple languages? #225

sr2ds opened this issue Apr 13, 2021 · 2 comments
Labels
website Change to site generator

Comments

@sr2ds
Copy link

sr2ds commented Apr 13, 2021

I think we could have a lang directory within content/docs with a new directory for each language.

 content/
    lang/
       fr/
       pt_br/
          application.md // all files translated for each language

In the sequence, it would be nice to have some language selector in the header, already based on the existing lang directories.

And to display the languages, I imagine that we will need to customize the layouts/code so that it renders the Content based on some URL parameter, for example.

https://actix.rs/docs/getting-started?lang=fr or https://actix.rs/docs/fr/getting-started/.

I don't know if it is a good way, they are just ideas so that we can simplify the process in the long run.

@robjtede robjtede added the website Change to site generator label Jul 5, 2022
@woile
Copy link
Contributor

woile commented Aug 15, 2022

The new website is using docusaurus, and it has support for i18n: https://docusaurus.io/docs/i18n/tutorial#translate-markdown-files

@Je12emy
Copy link

Je12emy commented Aug 24, 2023

I'm interested in contributing with a Spanish translation!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
website Change to site generator
Projects
None yet
Development

No branches or pull requests

4 participants