-
Notifications
You must be signed in to change notification settings - Fork 384
Set up structure and process for localization #33
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
Comments
Based on how we do it in expressjs.com, we'll need to create folders for each language under the This will also affect how we write links: we have to add a |
Here's a thread describing and linking to a number of different approaches for making multilingual sites with jekyll https://talk.jekyllrb.com/t/multi-language-strategies-with-jekyll/315 |
I think this is the best approach since it will work with GH Pages: https://www.sylvaindurand.org/making-jekyll-multilingual/ I like how it provides a language selector on each page. It's similar to what we use on http://expressjs.com/. I need to look into it a bit more to see how we would implement this with our Jekyll template; specifically, how we would add this to the layout templates that we have. |
I added a "Translations" dropdown selector in the top bar, and added some languages as examples. I documented the basic structure and process in:
I didn't add anything fancy (yet) to link to the other languages; We could make a number of improvements, but the basic setup is there to enable translation, so I'm going to close this issue. Let's add separate issues for any further improvements, or if there are problems with the current implementation. |
Need to establish a framework for localization. This includes:
The text was updated successfully, but these errors were encountered: