{"action":"created","issue":{"url":"https://api.github.com/repos/mozilla/teach.webmaker.org/issues/916","labels_url":"https://api.github.com/repos/mozilla/teach.webmaker.org/issues/916/labels{/name}","comments_url":"https://api.github.com/repos/mozilla/teach.webmaker.org/issues/916/comments","events_url":"https://api.github.com/repos/mozilla/teach.webmaker.org/issues/916/events","html_url":"https://github.com/mozilla/teach.webmaker.org/issues/916","id":76774247,"number":916,"title":"Forge a Globalization Strategy","user":{"login":"toolness","id":124687,"avatar_url":"https://avatars.githubusercontent.com/u/124687?v=3","gravatar_id":"","url":"https://api.github.com/users/toolness","html_url":"https://github.com/toolness","followers_url":"https://api.github.com/users/toolness/followers","following_url":"https://api.github.com/users/toolness/following{/other_user}","gists_url":"https://api.github.com/users/toolness/gists{/gist_id}","starred_url":"https://api.github.com/users/toolness/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/toolness/subscriptions","organizations_url":"https://api.github.com/users/toolness/orgs","repos_url":"https://api.github.com/users/toolness/repos","events_url":"https://api.github.com/users/toolness/events{/privacy}","received_events_url":"https://api.github.com/users/toolness/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-05-15T16:09:56Z","updated_at":"2015-05-15T16:13:33Z","closed_at":null,"body":"This issue is intended to document the **strategy** through which we'll make the Teach site possible to localize, rather than specific tooling to use for localization (#808).\r\n\r\nHere I'm using the word \"Globalization\" in the sense described by [Wikipedia](http://en.wikipedia.org/wiki/Language_localisation#Globalization_versus_localization):\r\n\r\n> Whereas localization is the process of adapting one product to a particular locale, globalization designs the product to minimize the extra work required for each localization.\r\n\r\nI'm going to go through every part of the current site in an attempt to address its globalization needs.\r\n\r\n## General\r\n\r\n* **Images** - Do we want to always present the same photos, e.g. pictures of Maurya and Mikko, to all locales, or will we want to present localized images to some locales?\r\n\r\n* **Social Media** - We mostly mention Twitter and Facebook on the site, but other countries may have different dominant social media networks. Should those localizations be able to tailor the display of social media information?\r\n\r\n* **Email** - At some points we tell visiors to email us at `teachtheweb@mozillafoundation.org`. Should this email address be used for all locales, or will some have locale-specific support email addresses?\r\n\r\n## Login\r\n\r\nWe'll likely want to communicate the currently-selected locale to id.webmaker.org, so that if the user manually set the site to Spanish but their browser indicates an English preference, they don't have to manually tell id.webmaker.org to be in Spanish too.\r\n\r\n## Sidebar\r\n\r\nThis should be pretty straightforward to localize, as all content is relatively short blurbs of text that are unlikely to change often.\r\n\r\n## Tabzilla\r\n\r\nI assume that Tabzilla is already localized. We'll just have to verify this, and then figure out how to communicate the user's currently-selected locale to Tabzilla, so that it shows its content in the same language.\r\n\r\n## Footer\r\n\r\nSimilarly straightforward to localize.\r\n\r\nFor links out to other Mozilla websites,  such as our Privacy Policy link, we should be sure to either link out to the *non-localized* version of the URL (e.g. without the `/en-US/` at the beginning of the path), or dynamically set the path locale based on the user's language setting on the Teach site.\r\n\r\nI'm also not sure what to do about the Twitter link. As I mentioned above, if a particular social media network is dominant in a particular locale, should this actually be a link to Mozilla Webmaker's presence on that social network, instead of Twitter?\r\n\r\n## Pages\r\n\r\n### Teaching Activities and Clubs Curriculum\r\n\r\nWhile the content on these pages is currently static, in the future, much of it probably won't be. We've [discussed](https://github.com/mozilla/teach.webmaker.org/issues/75#issuecomment-89069407) the likelihood for curriculum metadata to be pulled from a searchable database, rather than hard-coded into the HTML.\r\n\r\nIf the curriculum metadata here is ideally in a database rather than hard-coded into the site, I recommend migrating it into the database *before* adding support for localization to the Teach site. Otherwise we'll have to migrate all existing static localizations for the metadata into the DB, which will complicate the migration process.\r\n\r\nFurthermore, much of the content we're linking out to--such as the [Kraken The Code](http://mozilla.github.io/webmaker-curriculum/WebLiteracyBasics-I/session01-kraken.html) activity--is localized separately from the rest of the site. For example, while the Teach site itself might be localized in Spanish, the *Kraken The Code* activity may not be. If it *is* localized, then the Teach site should link directly to the Spanish version of the activity to provide a seamless transition. If it is *not* localized, we may want to consider warning users, e.g. by linking to \"Kraken El Código (en Inglés)\", or perhaps even omitting the link entirely.\r\n\r\n### Mozilla Clubs\r\n\r\nEverything except the actual club listing is pretty straightforward.\r\n\r\nHow should we go about localizing club listings? Will any clubs be bilingual? If they are, should the club leads be able to provide multiple translations for their club description?\r\n\r\nAssuming we can accurately detect what language a club description has been written in--either because the club lead explicitly told us, or because we used a tool like Google Translate to detect it for us--what will our strategy be for displaying the content to users? For instance, should a user in the Spanish locale be shown clubs whose descriptions are in English?\r\n\r\n### Teach Like Mozilla\r\n\r\nWow, if this page isn't changing anytime soon, this will be ridiculously easy to localize.\r\n\r\n### Web Literacy\r\n\r\nMy understanding is that the Web Literacy Map is actually already localized, so we should just pull from that. The main usability challenge here won't be for our end-users, but rather for localizers--if the existing process of localizing the Web Literacy Map is significantly different from the process for localizing the rest of the Teach site, it could frustrate people.\r\n\r\n### Maker Party\r\n\r\n#### Video\r\n\r\nIt seems YouTube is doing some kind of audio analysis to provide its own English captions, and then running those captions through Google Translate, but the results are kind of hilarious:\r\n\r\n![2015-05-15_11-49-55](https://cloud.githubusercontent.com/assets/124687/7656472/ac7660d4-faf8-11e4-96b1-ffe4131c8941.jpg)\r\n\r\nWe'll probably want to investigate how to actually provide accurate captions, and also decide whether we want our community to provide translations, or use YouTube's default translation capabilities.\r\n\r\nNote that this isn't just a localization issue--it's an accessibility concern as well.\r\n\r\n#### Mailing List\r\n\r\nWill there be different mailing lists for different locales? If the mailing list is English-only, should we warn non-English users about that?\r\n\r\n### Clubs Toolkit\r\n\r\nThis is a *lot* of content. Does it need to be merely translated, or is it likely that different locales will want to actually maintain separate versions of their content?\r\n\r\nFor example, are some bullet points not relevant in certain locales? I'm noticing that one bullet point links to [NWP Digital Is](http://digitalis.nwp.org/), which I assume won't be particularly useful for non-English (possibly even non-US) audiences.\r\n\r\nSimilarly, will some locales want to add additional bullet points specific only to them?\r\n\r\nThere are some mentions of Twitter here, which I have the same concerns about that I addressed in the \"General\" section above.\r\n\r\n### Event Resources\r\n\r\nThis is big.\r\n\r\n* **Event Guides** - Similar concerns as curriculum: if an event guide isn't available for a particular language, how do we deal with it?\r\n* **Logos and Assets** - Almost all of these have English text on them, and I assume they'll be very hard or impossible for our community to localize. My assumption is that, similar to teaching activities, the localizations of these assets will be a small subset of the localizations for the Teach site as a whole. If that's the case, do we want to  \"fall back\" on the English-language assets for a locale?\r\n* **Event Details** - I have the same concerns here that I do with the Clubs Toolkit above.\r\n\r\nPhew, I think that's it!\r\n"},"comment":{"url":"https://api.github.com/repos/mozilla/teach.webmaker.org/issues/comments/102450630","html_url":"https://github.com/mozilla/teach.webmaker.org/issues/916#issuecomment-102450630","issue_url":"https://api.github.com/repos/mozilla/teach.webmaker.org/issues/916","id":102450630,"user":{"login":"toolness","id":124687,"avatar_url":"https://avatars.githubusercontent.com/u/124687?v=3","gravatar_id":"","url":"https://api.github.com/users/toolness","html_url":"https://github.com/toolness","followers_url":"https://api.github.com/users/toolness/followers","following_url":"https://api.github.com/users/toolness/following{/other_user}","gists_url":"https://api.github.com/users/toolness/gists{/gist_id}","starred_url":"https://api.github.com/users/toolness/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/toolness/subscriptions","organizations_url":"https://api.github.com/users/toolness/orgs","repos_url":"https://api.github.com/users/toolness/repos","events_url":"https://api.github.com/users/toolness/events{/privacy}","received_events_url":"https://api.github.com/users/toolness/received_events","type":"User","site_admin":false},"created_at":"2015-05-15T16:13:33Z","updated_at":"2015-05-15T16:13:33Z","body":"I know we're committed to naming milestones after things from the 80's, but if we ever do a milestone where we focus on accessibility, I think it should be called **Make Your Party Is Missiles Campaign To Celebrate The Web**."}}