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

Set up structure and process for localization #33

Closed
crandmck opened this issue Aug 11, 2016 · 4 comments
Closed

Set up structure and process for localization #33

crandmck opened this issue Aug 11, 2016 · 4 comments

Comments

@crandmck
Copy link
Contributor

Need to establish a framework for localization. This includes:

@crandmck crandmck changed the title Set up structure and process for translation Set up structure and process for localization Aug 11, 2016
@crandmck
Copy link
Contributor Author

crandmck commented Aug 11, 2016

Based on how we do it in expressjs.com, we'll need to create folders for each language under the pages folder, for example en for English, de for German, zh for Chinese, etc.
These folders would then contain the docs in that language, e.g. lb2 and lb3 folders, for LoopBack 2.x and LoopBack 3. Some languages might decide to just have 3.0 content or 2.x content.

This will also affect how we write links: we have to add a lang property to the front-matter and {{page.lang}} to links.

@nuba
Copy link

nuba commented Aug 24, 2016

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

@crandmck
Copy link
Contributor Author

crandmck commented Aug 24, 2016

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.

@crandmck
Copy link
Contributor Author

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.

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

No branches or pull requests

2 participants