Closed Bug 801587 Opened 12 years ago Closed 12 years ago

Implement Firefox download on Firefox landing page

Categories

(support.mozilla.org :: Knowledge Base Software, task, P3)

Product:
support.mozilla.org
Component:
Knowledge Base Software
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2012Q4

People

(Reporter: atopal, Assigned: mythmon)

Details

(Whiteboard: u=user c=wiki p=1 s=2012.22) 

The Firefox landing page needs a button to download the app. See https://bug762255.bugzilla.mozilla.org/attachment.cgi?id=647857
The download button needs to link here: https://www.mozilla.org/en-US/products/download.html

We will NOT be implementing all the logic required for a download button that starts the download directly from SUMO.

Given that assumption, this is just some basic html+css => 1pt
Whiteboard: u=user c=wiki p= s=2012.21 → u=user c=wiki p=1 s=2012.21
(In reply to Ricky Rosario [:rrosario, :r1cky] from comment #1)
> The download button needs to link here:
> https://www.mozilla.org/en-US/products/download.html
No. It must depend on the locale. A French user doesn't want an English Firefox.
(In reply to Scoobidiver from comment #2)
> (In reply to Ricky Rosario [:rrosario, :r1cky] from comment #1)
> > The download button needs to link here:
> > https://www.mozilla.org/en-US/products/download.html
> No. It must depend on the locale. A French user doesn't want an English
> Firefox.

Good catch, it should go here: https://www.mozilla.org/products/download.html
(In reply to Ricky Rosario [:rrosario, :r1cky] from comment #3)
> Good catch, it should go here: https://www.mozilla.org/products/download.html
Not at all. This link is currently redirected to en-US.
(In reply to Scoobidiver from comment #4)
> (In reply to Ricky Rosario [:rrosario, :r1cky] from comment #3)
> > Good catch, it should go here: https://www.mozilla.org/products/download.html
> Not at all. This link is currently redirected to en-US.

seems like a bug on the mozilla.org side? Where do you go in french to download?
(In reply to Ricky Rosario [:rrosario, :r1cky] from comment #7)
> So, does http://www.mozilla.org/firefox/new/ work for everybody?
Yes (tested with major locales), but it will be a fake download button as it won't try to save a file but will redirect to another page. Bram expected a genuine download link.
In absence of the ability to download Firefox directly at the click of a button (because the OS, version and language logic is tricky), I agree with Ricky that the button should link to a download landing page that will work across locales.

Wonder if the design/creative team has an embeddable universal download button? My guess would be “no”, but they might have plans for something similar to this. Who’s a good point of contact for this subject?
I thought the download button usage was restricted to direct downloads, not for links to a download page. See http://www.mozilla.org/en-US/firefox/brand/website/

Why not a download link instead?
(In reply to Scoobidiver from comment #10)
> Why not a download link instead?

Because, a) I don't know if it's allowed. b) it isn't trivial to implement. c) taking them to the download page is fine since they are looking to download firefox and not get help from SUMO.

If we want to look into something more than a link to mozilla.org, we need to turn this into a research bug.
Target Milestone: --- → 2012Q4
The plan for this was always to have it be a regular mozilla download button like we include in many mozilla.org pages. Here's just one example http://www.mozilla.org/en-US/firefox/update/

Notice that it downloads the current Firefox for the user's OS. The button also includes links to:
http://www.mozilla.org/en-US/firefox/all.html
http://www.mozilla.org/en-US/firefox/notes
http://www.mozilla.org/en-US/legal/privacy/firefox.html

Is there a reason why we can't just use the same code?
(In reply to Verdi [:verdi] from comment #12)
> Is there a reason why we can't just use the same code?
There is a lot of magic behind that button. It needs to know what the latest firefox is, for example.

Turning this bug into a research bug to talk to mozilla.org folks about their code see if it is possible to reuse it in SUMO. Also, I don't know if there is some policy that download must be from mozilla.org or something like that?
Summary: Need Firefox download button on product landing page → [research] Implement Firefox download on Firefox landing page
The logic for the download button shouldn't be duplicated on other sites because we change the behavior from time to time in ways that would break your download button unless you followed our changes. For example, just recently we've been making a ton of changes to the download button to support the new stub installer: moving to HTTPS downloads for Bouncer, putting more products in Bouncer, serving up the stub installer to certain locales, etc.

If we changed the download button to be a separate library that other sites use, we'd have to commit to supporting old behavior for sites that don't keep the library up to date, which I'm not sure we're ready to do. 

cmore will have more info about policy, and Rik may have extra insight as well, but in general we don't want sites to duplicate the download button and just want them to link to the download page (Flicks did this in the header, for example: https://firefoxflicks.mozilla.org/en-US/judges).
(In reply to Michael Kelly [:mkelly] from comment #14)

That's what I thought, thanks for the info. In the case of sending users to mozilla.org for downloading, what would be the right page to send them to?
Wouldn't it be http://www.mozilla.org/firefox for desktop and http://www.mozilla.org/mobile for mobile?

We'd also have to do something about release notes. The idea for the IA was to include a link to the release notes on support with the download button. I guess that would be a different bug.
(In reply to Verdi [:verdi] from comment #16)
> Wouldn't it be http://www.mozilla.org/firefox for desktop and
> http://www.mozilla.org/mobile for mobile?

Looks right to me. A quick check in the primary locales you're concerned about might be useful to make sure it handles them correctly.
The link to Privacy Policy should be http://www.mozilla.org/legal/privacy/firefox.html and to Other Systems and Languages, http://www.mozilla.org/firefox/all.html
(In reply to Verdi [:verdi] from comment #16)
> Wouldn't it be http://www.mozilla.org/firefox for desktop and
> http://www.mozilla.org/mobile for mobile?

http://www.mozilla.org/firefox redirects me to http://www.mozilla.org/en-US/firefox/fx/ with the mobile tab selected. I think that http://www.mozilla.org/firefox/new/ would be a better link for desktop. 
 
> We'd also have to do something about release notes. The idea for the IA was
> to include a link to the release notes on support with the download button.
> I guess that would be a different bug.

Related discussion thread: https://support.mozilla.org/en-US/forums/contributors/708694?page=1#post-49155
Priority: -- → P3
Summary: [research] Implement Firefox download on Firefox landing page → Implement Firefox download on Firefox landing page
Whiteboard: u=user c=wiki p=1 s=2012.21 → u=user c=wiki p=1 s=2012.22
Assignee: nobody → mcooper
I implemented this as:

Main button: http://www.mozilla.org/firefox#desktop. (This shows "Hooray, you're up to date" if the user has an up to date or beta/aurora/nightly version of Firefox.

Three links below:
Privacy Policy: http://www.mozilla.org/legal/privacy/firefox
What's New: http://www.mozilla.org/en-US/firefox/notes
Systems and Languages: http://www.mozilla.org/firefox/all.html

This differs slightly from the mock up, to better conform to other Firefox download buttons.

This will land and get pushed out tomorrow morning, unless there are objections.
Is there a URL to check it out prior to tomorrow’s push? Otherwise, I think it will look good. Thanks, Mike!
Oh, I got thing mixed up, and I thought that Rik asked to look at things before it pushed. Sorry, Bram.

Pushed to production this morning.

It was pointed out that this doesn't look quite like the buttons in the style guide[1], and that we might want to tweak them to match in the near future.

[1]: http://www.mozilla.org/en-US/styleguide/websites/sandstone/buttons/
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Looks good to me! We should change the type to match the one found on the guideline with a new bug. “Firefox” is set using Georgia, and the rest of the text is Open Sans.
(In reply to Mike Cooper [:mythmon] from comment #21)
> I implemented this as:
> 
> Main button: http://www.mozilla.org/firefox#desktop. (This shows "Hooray,
> you're up to date" if the user has an up to date or beta/aurora/nightly
> version of Firefox.
> 
> Three links below:
> Privacy Policy: http://www.mozilla.org/legal/privacy/firefox
> What's New: http://www.mozilla.org/en-US/firefox/notes
> Systems and Languages: http://www.mozilla.org/firefox/all.html

(Probably a different bug, but) http://www.mozilla.org/en-US/firefox/notes still goes to http://www.mozilla.org/en-US/firefox/16.0.2/releasenotes/ instead of  http://www.mozilla.org/en-US/firefox/17.0/releasenotes/ ... even though 17.0 was released on Nov 20th.
Yeah, that is a redirect the mozilla.org team needs to change on their side. Nothing we can do about it in Kitsune.
(In reply to Alice Wyman from comment #25)
> (In reply to Mike Cooper [:mythmon] from comment #21)
> > I implemented this as:
> > 
> > Main button: http://www.mozilla.org/firefox#desktop. (This shows "Hooray,
> > you're up to date" if the user has an up to date or beta/aurora/nightly
> > version of Firefox.
> > 
> > Three links below:
> > Privacy Policy: http://www.mozilla.org/legal/privacy/firefox
> > What's New: http://www.mozilla.org/en-US/firefox/notes
> > Systems and Languages: http://www.mozilla.org/firefox/all.html
> 
> (Probably a different bug, but) http://www.mozilla.org/en-US/firefox/notes
> still goes to http://www.mozilla.org/en-US/firefox/16.0.2/releasenotes/
> instead of  http://www.mozilla.org/en-US/firefox/17.0/releasenotes/ ... even
> though 17.0 was released on Nov 20th.

This is no longer an issue as /firefox/notes redirects to 17.0.
You need to log in before you can comment on or make changes to this bug.