1075979 - localize new www.mozilla.org homepage redesign

Status: RESOLVED FIXED

(www.mozilla.org :: L10N, defect)

Description

[Jennifer Bertsch [:jbertsch]]

Hi-

We have a new design for the mozilla.org homepage!

The en-US verions will feature content from The Open Standard:  https://www-demo5.allizom.org/en-US/

All other locales, for now, will not feature Open Standard content:  https://www-demo5.allizom.org/de/

Note that the following locales will include the Twitter promo block:
@Firefox (en-US)
@Firefox_ES (all ES)
@FirefoxBrasil (pt-BR)

Locales that do have the current version of the homepage localized can remain on that version until they do localize to this new design.  Locales not currently localized will default to en-US until they localize this new design.

We recognize that the small tiles have very limited room for text.  Localizers have the freedom to create the best copy to fit that space while honoring the intent of the original copy and still promoting the destination content :)

Thanks so much for all your help.

-Jen

PS The launch date is October 15 and localization is not a blocker for launch.

Comment 1

[Francesco Lodolo [:flod]]

Before proceeding with string extraction, I think we need to fix one issue with the template structure
https://github.com/mozilla/bedrock/blob/implement-homepage-redesign/bedrock/mozorg/templates/mozorg/home/index.html

This file searches for a tag ('homepage_redesign_tos'), to determine if it needs to load the old template (mozorg/home.html) or the new one (mozorg/home/home-new.html).

But it would search for this tag in mozorg/home/index.lang, and then the new template would search for strings in mozorg/home/home-new.lang

We have two alternatives

1. Load both the tag and strings for new template from the existing mozorg/home.lang, adding to a directive to mozorg/home/index.html

> {% add_lang_files "mozorg/home" %}

2. Make mozorg/home/home-new.html load mozorg/home/index.lang

Second option would make clean-up easier in the future. Eventually we'll need to copy over some strings from mozorg/home.lang to mozorg/home/index.lang (haven't checked the template yet).

Pascal, any thoughts on this?

One other thing that I discussed briefly with agibson on IRC: layout can't accomodate long text. Take for example the small "Understand your privacy online" (light purple background). If you change the text with devtools, you'll see it disappears after the fourth line. If a single word is very long, it will bleed out of the box.

I understand we can try to fix this with ad-hoc CSS, but at least the bleeding of text should be fixed?

Comment 2

[Alex Gibson [:agibson]]

Thanks flod, let me know which option you prefer for the strings and I'll see to it.

As for the bleeding text on the small promos with longer strings - in this instance we can't make the promo boxes variable height. The design relies on the promo sizes all being a fixed height for alignment to the grid. Making the boxes variable height would completely break the layout. I could allow the text to overrun the boundaries of the box, but even then it would look broken and would only give one extra line. :(

I think the only thing we can do here is to alter the small promo spacing for all non-engligh locales using CSS. In the case of the privacy promo for example, we could move the graphic over to the left and alter the padding to create more space for the text. I think this is the only real solution.

The good thing is I believe that the smaller promos will not change very frequently.

Comment 3

[Alex Gibson [:agibson]]

I also have some updated strings from Jen to add. Once this is done and pushed to demo5, I'll needsinfo here for approval before we extract the strings.

Comment 4

[Pascal Chevrel (relman team) -> :pascalc]

let's use mozorg/home/index.lang (option 2)

Comment 5

[Francesco Lodolo [:flod]]

(In reply to Pascal Chevrel:pascalc from comment #4)
> let's use mozorg/home/index.lang (option 2)
Agreed.

@agibson: then we'll need to add this to mozorg/home/home-new.html
{% add_lang_files "mozorg/home/index" %}

https://github.com/mozilla/bedrock/blob/implement-homepage-redesign/bedrock/mozorg/templates/mozorg/home/home-new.html#L7
I don't think we need this line instead.

I know that the strings are not final, but just in case, this one is not wrapped
https://github.com/mozilla/bedrock/blob/implement-homepage-redesign/bedrock/mozorg/templates/mozorg/home/home-new.html#L144

How are the events going to be managed?
https://github.com/mozilla/bedrock/blob/implement-homepage-redesign/bedrock/mozorg/templates/mozorg/home/includes/upcoming-events.html

Comment 6

[Alex Gibson [:agibson]]

Thanks, Flod.

I've updated to include the lang file as above and also wrapped the string I missed (thanks for the spot!).

As discussed on IRC, we're using the Reps iCal feed to display the events on both the new home page and the contribute page. I've gone and added strings to the new home page template for the months of the year (full and abbreviated). But it may be worth having these in `main.lang` also as you suggest.

Comment 7

[Alex Gibson [:agibson]]

Hi Jen,

The updated strings you sent in your email are now up on demo5: https://www-demo5.allizom.org/en-US/

Can you please confirm here when they are all approved, so we can extract the strings?

Thanks

Comment 8

[Jennifer Bertsch [:jbertsch]]

Strings are not yet quite final.  I'll post here in the next hour or two when they are ready.

Comment 9

[Jennifer Bertsch [:jbertsch]]

Great news!  Strings are final!  Extract away and localize!  Thanks!

Comment 10

[Francesco Lodolo [:flod]]

No issues found in the template, just extracted the strings (39 strings, 203 words). Given the size of content, I expect to have a few locales to launch together with en-US.

Adding a note here too for future reference. Yesterday I added month names to main.lang, since they're used in both /contribute and new home page.

Then I realized that we can't distinguish "May" as full name from "May" as short name, so I asked Alex to use lowercase for short names (jan, feb, mar, etc.) and eventually fix the display with CSS for en-US. One downside of not having string IDs I guess.

Comment 11

[Francesco Lodolo [:flod]]

I think that we can close this one

Status tracking
https://l10n.mozilla-community.org/~pascalc/langchecker/?locale=all&website=0&file=mozorg/home/index.lang

Currently 34 locales enabled, 33 languages enabled on launch date.