Mozilla.org /firefox/firstrun/ - Copy for 40.0

RESOLVED FIXED

Status

Marketing
Copy
RESOLVED FIXED
3 years ago
2 years ago

People

(Reporter: cmore, Assigned: matej)

Tracking

Details

(Reporter)

Description

3 years ago
Placeholder bug for copy for the improved sync flow for 39.0.
(Reporter)

Updated

3 years ago
Blocks: 1150222
Is this going to be en-US only or will it need localization?
Flags: needinfo?(chrismore.bugzilla)
(Reporter)

Comment 2

3 years ago
(In reply to Liz Henry (:lizzard) from comment #1)
> Is this going to be en-US only or will it need localization?

It will be localized and we are going to try to re-use as many strings as possible that is going to be used in 38.0.5 and the existing FxA form.
Flags: needinfo?(chrismore.bugzilla)
flod, axel, just bringing you in so that you are aware of requests for localization in this feature. I just learned about it on Friday.
Flags: needinfo?(l10n)
Flags: needinfo?(francesco.lodolo)
I think we're talking about web parts (mozilla.org), not in-product strings, right?

In that case we try to ask for 3 weeks of lead time, especially if it involves a lot of locale.s
Flags: needinfo?(l10n)
Flags: needinfo?(francesco.lodolo)
Yes, I believe so. Chris is this all web page copy? Or is some of it meant to go into something in-product?
Flags: needinfo?(chrismore.bugzilla)

Comment 6

3 years ago
Is there a central point of information for what we're doing around 39?

With 38, 38.0.5, should we really make noise for 39? I'm curious how we're evaluating "updates should be silent" vs "we should brag about our stuff".
FYI we did it also for Firefox 37 and a few locales, wasn't exactly thrilled by the timing (38 was still scheduled as 38 on 12 May).
https://l10n.mozilla-community.org/~pascalc/langchecker/?locale=all&website=0&file=firefox/whatsnew-fx37.lang
(Reporter)

Comment 8

3 years ago
(In reply to Liz Henry (:lizzard) from comment #5)
> Yes, I believe so. Chris is this all web page copy? Or is some of it meant
> to go into something in-product?

Yes, all on www.mozilla.org and we are going to try to stick with the same strings as the upcoming 38.0.5 release.
Flags: needinfo?(chrismore.bugzilla)
(In reply to Chris More [:cmore] from comment #8)
> Yes, all on www.mozilla.org and we are going to try to stick with the same
> strings as the upcoming 38.0.5 release.

That would be great, also considering that we'll be in Whistler the week before release date.

For reference, these are the strings currently used
http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/locales/en-US/firefox/whatsnew_38.lang?revision=140565&view=markup
(Reporter)

Updated

3 years ago
Summary: Mozilla.org /firefox/firstrun/ - Copy for 39.0 → Mozilla.org /firefox/firstrun/ - Copy for 40.0
(Reporter)

Comment 10

3 years ago
I think we are good with copy on the page now. 

Jpetto/habber: string frozen now? Do we have any new strings in the page? (non-iframe).
Flags: needinfo?(jon)
Flags: needinfo?(hhabstritt.bugzilla)
Flags: needinfo?(francesco.lodolo)
Not sure why the NI. I think the plan is to hand-off strings by this Friday.
Flags: needinfo?(francesco.lodolo)

Comment 12

3 years ago
As all form headlines are contained in the iframe, there aren't any new strings in the bedrock template. Should be clean on that front.
Flags: needinfo?(jon)
(Reporter)

Comment 13

3 years ago
No new strings from fx38.0.5 release, so we are good on L10N for fx40. Thanks.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Flags: needinfo?(hhabstritt.bugzilla)
Resolution: --- → FIXED
I think I'm missing some information: can someone explain why we're talking about iframes? And, if strings are not on Bedrock, where are they?
Flags: needinfo?(jon)

Comment 15

3 years ago
(In reply to Francesco Lodolo [:flod] from comment #14)
> I think I'm missing some information: can someone explain why we're talking
> about iframes? And, if strings are not on Bedrock, where are they?

The major change from the 38.0.5 firstrun is that we're replacing the primary CTA with an embedded Firefox Accounts sign up form. This form sits in an iframe, and is served from outside of bedrock. The strings are in the fxa-content-server repo, e.g.

https://github.com/mozilla/fxa-content-server/blob/master/app/scripts/templates/marketing_snippet_ios.mustache
Flags: needinfo?(jon)
Comment hidden (spam)
You need to log in before you can comment on or make changes to this bug.