Language picker

[Fishrock123]

Now that #490 has landed and the related build/deployment work seems to be completed, we should be able to get the language groups once again more involved with the website.

We should also start thinking of a way to choose the language.

I'm not sure io.js's way was really that great. I know we discussed the flag thing before, but to me that is the most easily recognizable way.

We don't have to have that open a country list, but we can use it as a prompt for language nonetheless.

cc @nodejs/website
cc also @leo who may have some ideas?

[leo]

That seems like something that should be implemented with the next redesign. So it would be great if you could add it to this repo. More details here:

To keep things clear, I'd like all upcoming design-related issues to be forwarded to the design repo so that I can consider them while designing.

[Fishrock123]

Sure, I guess? But we kinda need it before then. Can't hold everything up for that.

one thing we could do if we're really getting translation efforts back up again is probe for the activeness of the i18n WGs

[fhemberger]

Quoting myself here from nodejs/iojs.org#235:

Flags != Languages.
We could add automatic redirection to the localized version based on the user's 'Accept-Language' header settings. There's an nginx module for that: http://wiki.nginx.org/AcceptLanguageModule

EDIT New link: https://www.nginx.com/resources/wiki/modules/accept_language/

I think it's the most reliable way to determine a user's language without the need for user interaction.

we should also probably assemble a separate team to control translation efforts. the iojs way wasn't the best

[leo]

@Fishrock123 Ahh, no problem! Didn't know that.

@fhemberger i wouldn't do it automatically though. maybe a hint from somewhere within the site asking if you want to switch to the version of the site in your language

[Fishrock123]

@ore https://github.com/nodejs/nodejs-ko is quite active.

---

Flags != Languages.

My point also, but we shouldn't have the selection be flags, only the initial, along with the Language indicator.

I.e.

[🇩🇪 DE] is a little more visible than [DE] for such a thing.

We could add automatic redirection to the localized version based on the user's 'Accept-Language' header settings. There's an nginx module for that: http://wiki.nginx.org/AcceptLanguageModule

I think it's the most reliable way to determine a user's language without the need for user interaction.

perhaps but idk if I'm comfortable not having an easy way to adjust it?

I'm willing to look into the nginx thing though

@Fishrock123 yeah, but that's one of the only ones 😞

[fhemberger]

@ore You still could add a cookie for example: "Nah, I want to browse the site in Klingon". In case we're adding a manual selection dropdown, this should be done anyway.

[fhemberger]

Link to the nginx module is now https://www.nginx.com/resources/wiki/modules/accept_language/
… and meh, it's a 3rd party module. Thought it was a core feature.