Closed Bug 609613 Opened 15 years ago Closed 15 years ago

Make static version of persona previews for new whatsnew page(s)

Categories

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

Product:
www.mozilla.org
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: sgarrity, Assigned: rik)

References

Details

There are three versions of the new whatsnew page to be tested: http://nova.stage.mozilla.com/en-US/firefox/3.6/whatsnew/ http://nova.stage.mozilla.com/en-US/firefox/3.6/whatsnew/nova-b/ http://nova.stage.mozilla.com/en-US/firefox/3.6/whatsnew/nova-c/ They all include an iframe from getpersonas.com for the persona previews (since personas only do live previews if the source domain is getpersonas.com). Apparently we can't do the test with the iframe, so we need to build a static copy of the persona previews on these pages. Maybe we should make a copy of /en-US/firefox/3.6/whatsnew/ to /en-US/firefox/3.6/whatsnew/nova-a/ as the control so we don't have to static-ify the personas in the real version of the page.
Blocks: 610792
Anthony, can you help out here? I heard you've done some work creating test pages for the homepage. Let us know if you need more details. Thanks!
Assignee: nobody → anthony
Adding to what Mike said, we need to get this resolved soon. We're due to launch the new site in 4 weeks, and we definitely need to figure out which version of this page is going to work best. Anthony, many thanks in advance if you can help!
To be clear, this is a 2nd priority, behind bug 610537.
I don't understand how this is a problem. Why can't we use the iframe for the test? Plus, if we put the getpersonas.com content in the page, we won't be able to have a preview on hover.
we need to use javascript to track hovers and clicks with our testing tool (SiteSpect). we can't insert JS in an iframe hosted on a different domain.
Thanks, that makes sense. Shouldn't we make a static copy of the what's new page in the trunk before doing that?
yeah, makes sense to me. As a side note, if Persona hover previews where whitelisted on Mozilla.com, this wouldn't be a problem and we could run a more representative experiment.
Anthony, do you have an ETA on this one? The sense of urgency is driven by the fact that this is one of the most critical pages to localize, yet the localizers can't start until the page content is finalized, and the page content can't be finalized until we know how the testing goes. Thanks!
I will have it ready for Monday. What should we say instead of "Roll over to try, click to apply"? I'm thinking out loud but can't we use an iframe (and so providing the functionality) and just see a black box in SiteSpect for this area of the page? I mean recording statistics on this area if it's not working is kind of irrelevant because users are not interacting with the real stuff. And it can even alter the usage of other parts of the page. What do you think?
(In reply to comment #9) > I will have it ready for Monday. Excellent, thanks. > What should we say instead of "Roll over to try, click to apply"? What will the functionality be, exactly? Am still a little confused on that. > I'm thinking out loud but can't we use an iframe (and so providing the > functionality) and just see a black box in SiteSpect for this area of the page? > > I mean recording statistics on this area if it's not working is kind of > irrelevant because users are not interacting with the real stuff. And it can > even alter the usage of other parts of the page. > > What do you think? Blake?
(In reply to comment #10) > What will the functionality be, exactly? Am still a little confused on that. If we don't use an iframe, it will look the same but it won't do anything when you hover them. And on click, the best we can do is link to the getpersonas.com details page. Blake, not using an iframe will also change the download pattern. iframes are loaded after the main page. With inline code, it will be loaded earlier.
@Anthony, I don't have a problem with the changed download pattern. As long as clicking on an preview is a decent proxy for hovering over a preview (a likely hypothesis), removing the iframe shouldn't significantly affect our results.
I'm not gonna be able to finish this today. Will do tomorrow. Blake, I'm not sure clicking is a good proxy. My guess of what people are doing is: Once they discover that hovering changed the browser's look, they will try hovering something else and "play". Without the iframe, the mouse moves and there is no incentive to play. So either they will focus more on other areas and affect our results or they will quit the page earlier and affect our results. BTW, for my personal culture, what are we measuring to determine if one page is more successful than another?
Awesome, thanks. Can we get these into testing soon?
(In reply to comment #13) > BTW, for my personal culture, what are we measuring to determine if one page is > more successful than another? Good question, Anthony. We want to use the version that best helps users: 1. discover Firefox benefits (try addons, personas, etc.) 2. create or maintain a relationship with us (via our Newsletter, Facebook and Twitter) We'll look at metrics like bounce rate of each, and the mix of interaction coming from the product and the social media areas.
Thanks Laura for the insights. I just thought of a way to get everything we want: the live personas and testing results from SiteSpect. We could use the postMessage API https://developer.mozilla.org/en/DOM/window.postMessage to communicate. We are in touch with Randy Bird from SiteSpect to see if it's possible.
I merged what we have to production in r77667 These should be live soon, http://www.mozilla.com/en-US/nova-test-596010/whatsnew-a.html http://www.mozilla.com/en-US/nova-test-596010/whatsnew-b.html http://www.mozilla.com/en-US/nova-test-596010/whatsnew-c.html (In reply to comment #18) > Thanks Laura for the insights. > > I just thought of a way to get everything we want: the live personas and > testing results from SiteSpect. We could use the postMessage API > https://developer.mozilla.org/en/DOM/window.postMessage to communicate. We are > in touch with Randy Bird from SiteSpect to see if it's possible. Sounds great, looking forward to the response. Getting rid of iframes would be ideal, but in the interest of time and scope, we should test what we have now.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Just a comment on the testing, it should only target users for Firefox 3.6.12. The message in this static pages is set to "Thanks for supporting Mozilla’s mission of encouraging openness, innovation and opportunity on the Web!". This is the message for users on 3.6.12. Others get a message to upgrade.
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.