Closed Bug 678442 Opened 13 years ago Closed 13 years ago

[One Mozilla] Just in Case, Persistent Download Message for Merged Site

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: christine.brodigan, Assigned: sgarrity)

References

()

Details

Steven,

Yo! We were thinking the same thing at the same time today. In response to comment #12 on bug https://bugzilla.mozilla.org/show_bug.cgi?id=676002

Do you think you could tweak the persistent messaging unit that we recently launched to upgrade users to work on mozilla.org's current home page (what will become the root of the merged site)?

We'd tweak the messaging just a little, so that in the event that the merge causes a drop in traffic or downloads, we could launch this unit as an interim patch on mozilla.org's home page.

It would work like https://support.mozilla.com/en-US/kb/firefox-takes-long-time-start-up?ref=aoa - but, have a download button/link, so users would know they have come to the right place for downloads.

Fred also cc'd, because I don't know what is needed for adding download capability to the site (I know it doesn't have it right now).

We would only launch this in the event that the merge caused a significant and sudden drop in downloads. It would essentially be "in our back pocket" to course correct, while we figure out what to do with the .org home page in the longer term (significantly more complicated).

Ideas?
Thanks Chrissie. I like the idea of having this as a backup in case we need it - better safe than sorry.

Couple of other thoughts:
- we should work with Matej and the PMMs to craft the copy
- if we can't enable downloads directly from this button, at least linking to the /firefox page would be an ok fallback
I did a quick experiment of porting the persistent download message for 3.6 users from mozilla.com (Bug 668101) over to the mozilla.org home page. Basically, it can work and isn't too much work on the tech/design side.

An actual functional download button would be no easier than getting one right in the mozilla.org home page (which I'll also look into).

If we can get the copy, we can put it together and have it ready as in case of post-merge calamity.
(In reply to John Slater from comment #1)
> - we should work with Matej and the PMMs to craft the copy

Sorry, not entirely clear on what the ask is here. Also, what's the timing?
I too am confused about what we're doing. More explanation svp?
(In reply to Laura Mesa [:lmesa] from comment #4)
> I too am confused about what we're doing. More explanation svp?

Sure. The background is that in our One Mozilla meeting yesterday, Chrissie and Steven raised the issue that the merge *could* eventually change traffic patterns on the site that *could* adversely affect downloads. For example, we have all the proper redirects in place for organic search or people who just type in mozilla.com, but if people who have been in the habit of typing in mozilla.com get in the habit of typing mozilla.org instead then they'll start getting a non-optimized download experience. That may be an edge case, but if it happens in significant numbers it may affect the download rate, at least a little bit (which still could equal a lot of downloads).

We'll be monitoring the numbers, and we do have a redesign of mozilla.org planned that will help a bit (although that page will never be optimized just for Fx downloads), but in the interest of having a contingency plan ready just in case we're proposing the plan in comment #0. That would give us the ability to slide down a little overlay in the style of https://support.mozilla.com/en-US/kb/firefox-takes-long-time-start-up?ref=aoa to call out Firefox a bit more strongly so it doesn't get lost on the page.

To be clear, our definite preference is to not use this, so it won't be a default or anything...just something in our back pocket in case we need it. I'm pretty confident that things will be fine, but better safe than sorry.

So, the copy request is that we need a line that would fit the context of that little drop-down from SUMO that would say something like "Looking to download Firefox? Click here." Obviously it should have a little more flavor than that, but the idea is that we're waving a little Firefox sign in a crowd to help people find their way.
Re: timing, I'm not sure...Chrissie or Steven, what do you think? Probably not like 5 minutes from now, but reasonably soon.
(In reply to John Slater from comment #5)
> (In reply to Laura Mesa [:lmesa] from comment #4)
> > I too am confused about what we're doing. More explanation svp?
> 
> Sure. The background is that in our One Mozilla meeting yesterday, Chrissie
> and Steven raised the issue that the merge *could* eventually change traffic
> patterns on the site that *could* adversely affect downloads. For example,
> we have all the proper redirects in place for organic search or people who
> just type in mozilla.com, but if people who have been in the habit of typing
> in mozilla.com get in the habit of typing mozilla.org instead then they'll
> start getting a non-optimized download experience. That may be an edge case,
> but if it happens in significant numbers it may affect the download rate, at
> least a little bit (which still could equal a lot of downloads).
> 
> We'll be monitoring the numbers, and we do have a redesign of mozilla.org
> planned that will help a bit (although that page will never be optimized
> just for Fx downloads), but in the interest of having a contingency plan
> ready just in case we're proposing the plan in comment #0. That would give
> us the ability to slide down a little overlay in the style of
> https://support.mozilla.com/en-US/kb/firefox-takes-long-time-start-
> up?ref=aoa to call out Firefox a bit more strongly so it doesn't get lost on
> the page.
> 
> To be clear, our definite preference is to not use this, so it won't be a
> default or anything...just something in our back pocket in case we need it.
> I'm pretty confident that things will be fine, but better safe than sorry.
> 
> So, the copy request is that we need a line that would fit the context of
> that little drop-down from SUMO that would say something like "Looking to
> download Firefox? Click here." Obviously it should have a little more flavor
> than that, but the idea is that we're waving a little Firefox sign in a
> crowd to help people find their way.

This helps a ton, thanks!  
Something like ""Looking to download Firefox? Click here." is heading in the right direction and I'm happy to work with you Matej in anyway I can. I want to make sure we try including some product differentiators in there. Like our "super speed" or "new look". And as always, words like "free" and "fast download" have helped improve download conversions in the past.
Thanks guys, that clears things up. I'll give this a think and come up with some options. Laura, I'll let you know if I need any more direction.
(In reply to Matej Novak [:matej] from comment #8)
> Thanks guys, that clears things up. I'll give this a think and come up with
> some options. Laura, I'll let you know if I need any more direction.

Matej,

I'd look towards keeping the copy as close to tweet-sized as possible ;-) Do you know when you might have something ready for Steven?

Steven,

Realistically, we should have this ready to ship for the 3.7 release, week of August 22. 

How possible do you guys think that is? 

~cb
OK, here are a few options. Any of these headed in the right direction?


Looking for Firefox? Download it here. It's fast and free!

Get the browser you're looking for. Download Firefox here.

For speed, security and super awesomeness, download Firefox here.

Want Firefox? Great choice! Get it here.

The speed and sleek look of Firefox are only a click away.

Fast, free, Firefox. Download it here.

Runs fast, looks great. Download Firefox now.
I vote for either of the first 2, in this case i think it's best to keep the message simple and not too taglin-ey
(In reply to Matej Novak [:matej] from comment #10)
> OK, here are a few options. Any of these headed in the right direction?
> 
> 
> Looking for Firefox? Download it here. It's fast and free!
> 
> Get the browser you're looking for. Download Firefox here.
> 
> For speed, security and super awesomeness, download Firefox here.
> 
> Want Firefox? Great choice! Get it here.
> 
> The speed and sleek look of Firefox are only a click away.
> 
> Fast, free, Firefox. Download it here.
> 
> Runs fast, looks great. Download Firefox now.

I like the first two, but prefer the first one above all.
+1 for #1. (but I also like #2)

Matej, do you have a preference?
I think asking the question is probably stronger here, and I agree about the simple, straightforward approach, so I think #1 works great.
(In reply to John Slater from comment #13)
> +1 for #1. (but I also like #2)
> 
> Matej, do you have a preference?

My preference: Fast, free, Firefox. Download it here.

High readability, because the user won't have to read different sounding words (everything starts with F). That might sound silly, but ux-wise it's very smart.

Here = call to action (again, less thinking involved for the user).
#1 it is!

Steven, can we style this with a little Firefox icon in there? Is there room for an actual (small) download button?
(In reply to mcbmoz from comment #9)
> Realistically, we should have this ready to ship for the 3.7 release, week
> of August 22.  How possible do you guys think that is? 

Yeah, we can have it ready

(In reply to John Slater from comment #16)
> Steven, can we style this with a little Firefox icon in there? Is there room
> for an actual (small) download button?

We probably can't get a functional locale-detecting download button in there by next week, but we can put a button-style link (in this style: http://moz.howsehold.org/sumo/upgrade/top.html)
Blocks: 610724
Since mozilla.org doesn't have a stage site, I've got this implemented in production (r94204), but turned off. You can enable it with  URL var:

http://www.mozilla.org/?fallbackmsg=1

Visual, there's a lot going on up here in the header now. Suggestions are welcome - do keep in mind though, that we hopefully won't need to use this, and that we don't have much time.
Keywords: qawanted
OS: Mac OS X → All
Hardware: x86 → All
Thank you Steven & Raymond, I think the only thing left is how we would deploy this (if needed). Fred, would that be something you would be able to do?
(In reply to mcbmoz from comment #20)
> Thank you Steven & Raymond, I think the only thing left is how we would
> deploy this (if needed). Fred, would that be something you would be able to
> do?

I've added the following lines (r94207):

    // Uncomment the following line to enable fallback download message
    // $showfallback = 1;
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Thanks, Steven! (Don't do an ugly hack like this inside a template when we switch to bedrock though ;))
Thanks Steven. This looks good to me too.
I'll leave this code in for now, but since we didn't deploy this we might be able to remove it soon.
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.