1213372 - update footer copy on /new

Status: RESOLVED FIXED

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

Description

[Jennifer Bertsch [:jbertsch]]

Hi-

Cmore and I would like to make the following changes to /new, pending review by habber.

1.  Delete the line in the footer with "Tour...About" and move up the 2 copy lines below
2.  Remove "Systems & Languages" and "What's New" from the area inbetween the download button and the browser image and change "Privacy" to ""Firefox Browser Privacy Notice" (see attached screenshot - the string should be localized here https://www.mozilla.org/en-US/privacy/firefox/)

Comment 1

[Jennifer Bertsch [:jbertsch]]

3.  Under "Privacy | Cookies | Legal" in the footer, insert a new line of copy with "Add-Ons | Release Notes (English) | Download Firefox for Other Platforms and Languages (English)" and those will now links to the main add-ons page, release notes, and the /all page.  Note:  these strings will need L10N

Comment 2

[Jennifer Bertsch [:jbertsch]]

Attachment: firefoxbrowserprivacynotice.png

Holly and Matej - could you please review the changes proposed in comments 0 and 1?  Thanks!

Comment 3

[Matej Novak [:matej]]

Good by me. Thanks.

Comment 4

[Holly Habstritt Gaal [:Habber]]

Keep in mind that the Systems & Languages link as well as Release Notes link will need to be specific to the user landing on the page. They may be viewing from Desktop, iOS, or Android. One /all/ or release notes URL will not support every user who lands on /new. When the links were near the download button, this logic was handled. 

https://www.mozilla.org/en-US/firefox/all/ is desktop specific. 

https://www.mozilla.org/en-US/firefox/android/all/ is Android specific.

I do not see a Systems & Languages page for iOS.


What is desired outcome of removing it from where it is now? Less links to distract users from the download button? Do we want to put this kind of conditional logic in the footer?

Comment 5

[Jennifer Bertsch [:jbertsch]]

(In reply to Holly Habstritt Gaal [:Habber] from comment #4)
> Keep in mind that the Systems & Languages link as well as Release Notes link
> will need to be specific to the user landing on the page. They may be
> viewing from Desktop, iOS, or Android. One /all/ or release notes URL will
> not support every user who lands on /new. When the links were near the
> download button, this logic was handled. 
> 
> https://www.mozilla.org/en-US/firefox/all/ is desktop specific. 
> 
> https://www.mozilla.org/en-US/firefox/android/all/ is Android specific.
> 
> I do not see a Systems & Languages page for iOS.
> 
> 
> What is desired outcome of removing it from where it is now? Less links to
> distract users from the download button? Do we want to put this kind of
> conditional logic in the footer?

The desired outcome is to deprioritze the /all and release notes links on the page.

Jpetto and agibson - what do you think about how we should handle the logic?  Should we rethink this?

Comment 6

[Alex Gibson [:agibson]]

Hi Jen,

I'm not quite clear what you're asking for specifically here, but these links are currently pulled directly from the download button [1] itself, so they only appear for desktop. We don't have equivalent pages for all of these links for iOS/Android, because in some cases those pages don't exist.

[1] https://github.com/mozilla/bedrock/blob/master/media/js/firefox/new.js#L136-L140

Comment 7

[Jennifer Bertsch [:jbertsch]]

Hi Alex-

We have links to /all (https://www.mozilla.org/en-US/firefox/android/all/) and release notes (https://www.mozilla.org/en-US/firefox/android/41.0/releasenotes/) for Android around the download load button on /firefox/android but maybe that logic is hard coded on this page and not in the download button?

We would like to decouple these two links from the download button.

So my question is:  Does it add too much complexity to the page to have these links be conditional by platform within in the page vs within the download button?

Thx,
Jen

Comment 8

[Alex Gibson [:agibson]]

(In reply to Jennifer Bertsch [:jbertsch] from comment #7)
> Hi Alex-
> 
> We have links to /all (https://www.mozilla.org/en-US/firefox/android/all/)
> and release notes
> (https://www.mozilla.org/en-US/firefox/android/41.0/releasenotes/) for
> Android around the download load button on /firefox/android but maybe that
> logic is hard coded on this page and not in the download button?
> 
> We would like to decouple these two links from the download button.
> 
> So my question is:  Does it add too much complexity to the page to have
> these links be conditional by platform within in the page vs within the
> download button?
> 
> Thx,
> Jen

I believe these links are all generated by the download button app. Currently on the /new page we are relocating them for desktop users, which is a bit of a hack. We could do the same for Android users too, but ideally it would be good not to have to do this kind of thing too much as it becomes quite messy. 

If these links are no longer being prioritized next to download buttons, then is it something we should really be doing across all of mozorg and not just on an ad-hoc basis? 

I understand we want people to click the download button, but I do believe these links are also still valuable to users and are already quite minimal.

Comment 9

[Alex Gibson [:agibson]]

Sorry, I missed the bit about relocating the download button links to the page footer (I thought we we're just proposing to get rid of them). We would need to find some way to facilitate this for the appropriate platforms Holly mentions. Not sure what that would entail without looking into it a bit further. Also please keep in mind this is a shared footer which appears on more than one page.

Comment 10

[Jennifer Bertsch [:jbertsch]]

(In reply to Alex Gibson [:agibson] from comment #9)
> Sorry, I missed the bit about relocating the download button links to the
> page footer (I thought we we're just proposing to get rid of them). We would
> need to find some way to facilitate this for the appropriate platforms Holly
> mentions. Not sure what that would entail without looking into it a bit
> further. Also please keep in mind this is a shared footer which appears on
> more than one page.

Hi Alex-

It is fine that this is a shared footer that appears on more than one page.  I think the changes are appropriate for all those use cases (assuming it is primarily download/transactional Firefox pages).

If you think it is better to simplify the logic of these links, please propose that.  Obviously, the logic shouldn't stay tied to the download button any more.

Thanks,
Jen

Comment 11

[Alex Gibson [:agibson]]

Looking at the download button code I don't think it should be too much trouble to generate the same links in the footer and show them based on platform. We'll just need to scope out how many pages the shared footer is used on, and make sure the links are still appropriate.

Comment 12

[Jonathan Petto [:jpetto]]

I'm on board with decoupling the platform links from the download button. That moves us in a direction of a simpler button, which is a win in my book.

As agibson mentioned, we would then need to decide what to do across mozilla.org, as decoupling the links from the button would have a wide ranging effect.

Perhaps the download button helper could take an optional parameter indicating whether or not to include the platform links (which would be generated by a yet to be made function)?

Is moving these links away from the button a direction we're heading in general, or only for a couple pages? Are we proposing a new normal?

Comment 13

[Jennifer Bertsch [:jbertsch]]

(In reply to Jon Petto [:jpetto] from comment #12)
> I'm on board with decoupling the platform links from the download button.
> That moves us in a direction of a simpler button, which is a win in my book.
> 
> As agibson mentioned, we would then need to decide what to do across
> mozilla.org, as decoupling the links from the button would have a wide
> ranging effect.
> 
> Perhaps the download button helper could take an optional parameter
> indicating whether or not to include the platform links (which would be
> generated by a yet to be made function)?
> 
> Is moving these links away from the button a direction we're heading in
> general, or only for a couple pages? Are we proposing a new normal?

We are proposing a new normal - moving the links away from the button and into the footer.  I like what Alex is proposing in comment 11.

Comment 14

[Jennifer Bertsch [:jbertsch]]

Let's move forward with implementing this footer on /new in Sprint 4 starting March 14

Comment 15

[Jennifer Bertsch [:jbertsch]]

Notes based on conversation with Holly and Schalk:
1.  Firefox Privacy Notice needs to stay near button
2.  Systems & Languages and What's New become Release Notes (English) | Download Firefox for Other Platforms and Languages (English)

Comment 16

[Jennifer Bertsch [:jbertsch]]

(In reply to Jennifer Bertsch [:jbertsch] from comment #15)
> Notes based on conversation with Holly and Schalk:
> 1.  Firefox Privacy Notice needs to stay near button


> 2.  Systems & Languages and What's New become Release Notes (English) |
> Download Firefox for Other Platforms and Languages (English)  MOVE TO FOOTER

Comment 17

[Schalk Neethling [:espressive]]

(In reply to Jennifer Bertsch [:jbertsch] from comment #16)
> (In reply to Jennifer Bertsch [:jbertsch] from comment #15)
> > Notes based on conversation with Holly and Schalk:
> > 1.  Firefox Privacy Notice needs to stay near button
> 
> 
> > 2.  Systems & Languages and What's New become Release Notes (English) |
> > Download Firefox for Other Platforms and Languages (English)  MOVE TO FOOTER

Is this for desktop only? Asking because android and ios has a "supported devices" link, do we move that to the footer as well?

Comment 18

[Jennifer Bertsch [:jbertsch]]

(In reply to Schalk Neethling [:espressive] from comment #17)
> (In reply to Jennifer Bertsch [:jbertsch] from comment #16)
> > (In reply to Jennifer Bertsch [:jbertsch] from comment #15)
> > > Notes based on conversation with Holly and Schalk:
> > > 1.  Firefox Privacy Notice needs to stay near button
> > 
> > 
> > > 2.  Systems & Languages and What's New become Release Notes (English) |
> > > Download Firefox for Other Platforms and Languages (English)  MOVE TO FOOTER
> 
> Is this for desktop only? Asking because android and ios has a "supported
> devices" link, do we move that to the footer as well?

If we can show the Android and iOS links on mobile-focused pages, let's do it.

Comment 19

[Jennifer Bertsch [:jbertsch]]

Hi Alex-

Let's implement comments 0 and 1 above as part of the space theme redesign.

Thx
Jen

Comment 20

[Alex Gibson [:agibson]]

After discussion on IRC, we may be breaking this bug into separate bits of work that need to happen first, and will not hold up the redesign variation test.

Comment 21

[Jonathan Petto [:jpetto]]

To clarify, the ask of this bug is to take changes coming in bug 1259211 and incorporate them on /firefox/new/.

When bug 1259211 is complete, the following changes should be implemented on /firefox/new/:

- Remove footer links, e.g. "Tour, Features, Mobile, Add-Ons, Support, About"

- Underneath the bottom-most links ("Privacy | Cookies | Legal"), add the following links (based on platform):

    - Linux/OS X/Windows
        - Add-Ons (link to https://addons.mozilla.org/)
        - Desktop "other" links (see bug 1259211)
    - Android
        - Add-Ons (link to https://addons.mozilla.org/android/)
        - Android "other" links (see bug 1259211)
    - iOS
        - iOS "other" links (see bug 1259211)

Comment 22

[Holly Habstritt Gaal [:Habber]]

(In reply to Jennifer Bertsch [:jbertsch] from comment #15)
> Notes based on conversation with Holly and Schalk:
> 1.  Firefox Privacy Notice needs to stay near button
> 2.  Systems & Languages and What's New become Release Notes (English) |
> Download Firefox for Other Platforms and Languages (English)


In English, the above link titles in #2 are very long. In typically verbose languages like German, they will take up quite a bit of space in the footer. 
Example - https://irccloud.mozilla.com/file/AUzkVheM/Screen+Shot+2016-03-31+at+17.16.58.png
Example - https://irccloud.mozilla.com/file/2IOI3ALw/Screen+Shot+2016-03-31+at+17.25.37.png

Espressive, Mham, and I discussed this and would like to propose the following minor update to the link copy:
- "Release Notes" instead of "Release Notes (English)"  

- "Firefox for Other Platforms & Languages" instead of "Download Firefox for Other Platforms and Languages (English)"


Our rationale is that we don't have a precedent of setting up every non-translated page link with "(English)" behind it. Also, if these are important pages, we should consider making them a priority to get translated. Access to a "Download" should be implied in the second link. Shortening these links will help the readability and as a result usability for users seeking the information that they offer. 

Is it possible to move forward with the above copy suggestion?

Comment 23

[Jennifer Bertsch [:jbertsch]]

(In reply to Holly Habstritt Gaal [:Habber] from comment #22)
> (In reply to Jennifer Bertsch [:jbertsch] from comment #15)
> > Notes based on conversation with Holly and Schalk:
> > 1.  Firefox Privacy Notice needs to stay near button
> > 2.  Systems & Languages and What's New become Release Notes (English) |
> > Download Firefox for Other Platforms and Languages (English)
> 
> 
> In English, the above link titles in #2 are very long. In typically verbose
> languages like German, they will take up quite a bit of space in the footer. 
> Example -
> https://irccloud.mozilla.com/file/AUzkVheM/Screen+Shot+2016-03-31+at+17.16.
> 58.png
> Example -
> https://irccloud.mozilla.com/file/2IOI3ALw/Screen+Shot+2016-03-31+at+17.25.
> 37.png
> 
> Espressive, Mham, and I discussed this and would like to propose the
> following minor update to the link copy:
> - "Release Notes" instead of "Release Notes (English)"  
> 
> - "Firefox for Other Platforms & Languages" instead of "Download Firefox for
> Other Platforms and Languages (English)"
> 
> 
> Our rationale is that we don't have a precedent of setting up every
> non-translated page link with "(English)" behind it. Also, if these are
> important pages, we should consider making them a priority to get
> translated. Access to a "Download" should be implied in the second link.
> Shortening these links will help the readability and as a result usability
> for users seeking the information that they offer. 
> 
> Is it possible to move forward with the above copy suggestion?

Yes.  It is OK to move forward with those copy suggestions.

Release notes isn't localized because localizing them would be very technical and time consuming.

/all isn't localized for historical reasons that I don't remember specifically but that are logical.  (Pascal knows the full history)

Comment 24

[Schalk Neethling [:espressive]]

Logic for the footer links are as follows:

The links I am referring to are:

Firefox for Other Platforms & Languages
Release Notes
Supported Devices

-------

First, these will appear only on products pages.

Secondly, for the following pages, it will show the links for the product platform, not the viewing platform:

/firefox/desktop
/firefox/all
firefox/[ver]/releasenotes/

/firefox/android
firefox/android/all/
firefox/android/[ver]/releasenotes/

/firefox/ios
firefox/ios/]ver]/releasenotes/

firefox/developer/
firefox/developer/all/
firefox/[ver]/auroranotes/

i.e. If viewing /firefox/desktop on an Android device, the links in the footer will still be for desktop Firefox. Viewing /firefox/android will show the Firefox for Android links even when viewed on a desktop browser.

For:

/firefox/new/?scene=1
/firefox/new/?scene=2

The links in the footer will match the viewing platform so, viewing the page on Android, will show links for Android, viewing on desktop will show desktop etc.

These links will not be shown on any other pages.

Comment 26

[[github robot]]

Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/b58d262d4845389cd661afdda9e51e15d73c3082
Fix Bug 1213372, move secondary links to footer, download button styling and logic

https://github.com/mozilla/bedrock/commit/9e87f20339daf75deede359124f80413b2878aa6
[Bug 1213372] Move secondary links to footer, download button styling and logic

https://github.com/mozilla/bedrock/commit/5d322902d0f002f26d9a212bac820d253ffd5371
Merge pull request #4102 from mozilla/bug1213372-download-button-rework

[Bug 1268572] The big download button overhaul