Closed Bug 1205357 Opened 9 years ago Closed 9 years ago

Fall Campaign Landing Page - Implementation

Categories

(www.mozilla.org :: Pages & Content, defect)

Production
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ckprice, Assigned: espressive)

References

()

Details

(Whiteboard: [kb=1850274] [fall-2015-engagement])

Attachments

(1 file)

This bug executes the development for the Fall campaign landing page. Designs are in bug 1205356.
Whiteboard: [fall-2015-engagement] → [kb=1850274] [fall-2015-engagement]
Assignee: nobody → schalk.neethling.bugs
Status: NEW → ASSIGNED
Designs/copy final in bug 1205356
So, the heading strings in the concepts were much longer than the final strings and having it wrap, made sense. With the final strings I am unsure whether want to wrap them explicitly or, have them on one line, except for smaller viewport where it will naturally wrap. Which is preferred?
Flags: needinfo?(cprice)
Final URL is /firefox/choose/ Working on an answer to your headline question.
(In reply to Schalk Neethling [:espressive] from comment #3) > So, the heading strings in the concepts were much longer than the final > strings and having it wrap, made sense. With the final strings I am unsure > whether want to wrap them explicitly or, have them on one line, except for > smaller viewport where it will naturally wrap. > > Which is preferred? Hi Schalk, The team met, and we think it would be best if we broke the line ourselves. So Browse freely. Choose Firefox. etc. This is on the assumption that the headlines of the two supporting blurbs (The most private browsing, etc) are still above the fold (which from the designs in comment 2, seems to be the case). Thanks! NI espressive to make sure it's caught, since we're late on this one.
Flags: needinfo?(cprice) → needinfo?(schalk.neethling.bugs)
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Got it, thanks!
Flags: needinfo?(schalk.neethling.bugs)
Where should the links for the two blurbs point to? 1) "Learn more about this" 2) "Get smart on data tracking"
Flags: needinfo?(cprice)
(In reply to Schalk Neethling [:espressive] from comment #7) > Where should the links for the two blurbs point to? > > 1) "Learn more about this" https://mozilla.org/firefox/private-browsing/ (this page: bug 1196569) > 2) "Get smart on data tracking" NI malexis, jbertsch - do we know the URL for this page?
Flags: needinfo?(cprice)
Status: RESOLVED → REOPENED
Flags: needinfo?(malexis)
Flags: needinfo?(jbertsch)
Resolution: FIXED → ---
+Craig for Smart on tracking protection URL
Flags: needinfo?(jbertsch) → needinfo?(craigcook.bugz)
(In reply to Jennifer Bertsch [:jbertsch] from comment #9) > +Craig for Smart on tracking protection URL It will be: mozilla.org/teach/smarton/tracking/ or for Python: {{ url('teach.smarton.tracking') }} However, the Python URL will of course throw an error until the page is defined, so you'll probably want to put in a placeholder and make a note to update it once the smarton tracking page lands in master.
Flags: needinfo?(malexis)
Flags: needinfo?(craigcook.bugz)
Copy document has been updated with <title> and <description> https://docs.google.com/document/d/1BN0brWqkOK5-HE_uP1EzR0amVq_uWwonDNo_46HKe6k/edit Flod: the team was fine with both of these that were already in the template (still trying to track down where these came from). However, some of the formatting on the <title> needs updating (lower case B on browser).
Firefox Web Browser -> Firefox Web browser This string (with uppercase Browser) was already used in another page https://www.mozilla.org/en-US/firefox/independent/ "Keep your identity yours with the new Firefox" lost the final period. As minor as they look, both changes invalidate the existing translations (16 locales so far). We can: 1. Put a conditional in the template to use the new strings only in en-US. 2. Update the reference strings and keep the existing localizations. 3. Expose new strings for title and description. In this case, we can also use completely different strings since we're already breaking string freeze. If we go with #3, please provide the new strings as soon as possible.
Hi Flod, Given that the period and the hyphen are changing, we need to go with #3. Copy document has been updated. Firefox Web browser — Keep your identity yours with the new Firefox — Mozilla Sorry for the change here. Not entirely sure how these strings made it into the template (although we should have had it in the copy document).
> Firefox Web browser — Keep your identity yours with the new Firefox — Mozilla @espressive Is it technically possible to expose this a single string (the Private Browsing landing page is doing it)? In the past we had requests to avoid using "—" as hard-coded separator in the title, exposing one string for the entire title would help with that.
Flags: needinfo?(schalk.neethling.bugs)
(In reply to Francesco Lodolo [:flod] from comment #14) > > Firefox Web browser — Keep your identity yours with the new Firefox — Mozilla > > @espressive > Is it technically possible to expose this a single string (the Private > Browsing landing page is doing it)? In the past we had requests to avoid > using "—" as hard-coded separator in the title, exposing one string for the > entire title would help with that. WE can expose it as such: "Firefox Web browser — Keep your identity yours with the new Firefox — Mozilla" - means the — will be part of the string though. If that is fine, I can change it to be so.
Flags: needinfo?(schalk.neethling.bugs)
(In reply to Schalk Neethling [:espressive] from comment #15) > WE can expose it as such: > > "Firefox Web browser — Keep your identity yours with the new Firefox — > Mozilla" - means the — will be part of the string though. If that is fine, I > can change it to be so. On second thoughts, let's expose 2 strings Firefox Web browser Keep your identity yours with the new Firefox While it's nice to make "—" localizable, I also don't want locales to mess with the title structure. I'll keep the existing translations and ask localizers to double check them.
Commits pushed to master at https://github.com/mozilla/bedrock https://github.com/mozilla/bedrock/commit/129f74e9321d13f613c8be79af6670e0f7f8784f Fix Bug 1205357, implement fall campaign landing page https://github.com/mozilla/bedrock/commit/e33267437606c3d849e1306000921f353ba0a50a Merge pull request #3354 from schalkneethling/bug1205357-fall-campaign-landing-page Fix Bug 1205357, implement fall campaign landing page
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
Blocks: 1213891
Blocks: 1214232
No longer blocks: 1214232
I was doing some string searches on "Get smart on Tracking", and found out that the link on the landing page is pointing to privacy/tips https://github.com/mozilla/bedrock/blob/master/bedrock/firefox/templates/firefox/choose.html#L64 Is it wanted?
Flags: needinfo?(cprice)
Found my answer in bug 1213891 thanks to :agibson.
Flags: needinfo?(cprice)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: