Port Literacy page translations

[hannahkane]

The Web Literacy page has been translated previously, so we need to port those translations to the new Teach design.

• Determine mechanism for doing this technically
• Identify if any changes were made to the copy during the transition - i.e. is there a delta that needs to be translated in every language? (Update: yes, see below)
• Provide UX or browser locale detection to serve up the right translation to users

[toolness]

It seems like that third checkbox, "Provide UX or browser locale detection to serve up the right translation to users", should ultimately be global to the whole site, i.e. the weblit page shouldn't have a separate "choose your language" selector from the rest of the site. Er, unless it might be the case that the weblitmap is actually localized in more languages than the rest of the site, in which case we'll have to figure something out. I just added a note about this in #916.

[hannahkane]

Agreed that the ultimate solution should apply to the site globally. If we localize sections of the site in phases, we'll need an interim solution, though, right?

[toolness]

Um as a side note, this is how the current Web Literacy page on webmaker.org looks on Google:

... so we should make sure our result never ever looks like that.

[toolness]

Ack.

Ok, I started working on a solution for this in #964, but then I noticed your second checkbox, "Identify if any changes were made to the copy during the transition "... And it looks like our Transifex weblitmap resource is unfortunately for the legacy version 1.1 of the map, not the newer version 1.5 which was recently released on March 20.

Um, I also didn't notice that there's apparently a web-literacy-client github project that might have obviated the need for me to start my PR at all... Oh well.

Anyways, the fact that we don't have any translations of v1.5 of the literacy map sort of puts us back at the drawing board, unfortunately--my assumption was that this was going to be relatively easy because the translations already exist, but this isn't the case, so there isn't really that much of a difference in localizing this content versus localizing the rest of the site--with the exception, I suppose, that this content is extremely unlikely to change any time soon, while the rest of the site's content is under a lot of flux.

Hmmmm.

[toolness]

... this content is extremely unlikely to change any time soon, while the rest of the site's content is under a lot of flux.

Er, as hannah just pointed out on our daily stand, the web literacy map strings might not be so stable either, as Mark's latest blog post has the following photo in it: