User:Lmesa: Difference between revisions

Jump to navigation Jump to search

User:Lmesa (view source)

Revision as of 21:36, 10 August 2009

4,320 bytes removed ,  10 August 2009
Replaced content with '*Projects for Q3 **Mozilla.com Optimization ***Install/Update Content Optimization ***Plug-Ins **IE Switch page: SFx **Customer Satisfaction Survey **Hispanic Community'
(Replaced content with '*Projects for Q3 **Mozilla.com Optimization ***Install/Update Content Optimization ***Plug-Ins **IE Switch page: SFx **Customer Satisfaction Survey **Hispanic Community')
Line 1: Line 1:
= all.html Redesign =
*Projects for Q3


== Morgamic & Laura Discussion ==
**Mozilla.com Optimization
Crunchy schedule:
***Install/Update Content Optimization
* Dec 1 - Final design and PSD original files
***Plug-Ins
* Dec 5 - Option 2
**IE Switch page: SFx
* Dec 12 - Option 3
**Customer Satisfaction Survey
* Dec 19 - Option 1
**Hispanic Community
 
Problems:
* too close together
* not enough time for QA
* no padding for unexpected problems or feature changes
* webdev is saturated for Q4 right now
* Steven G - unsure of how available he is and whether or not he could stick to this type of schedule
* A/B testing not done either way
* Final launch is already pushed into Q1
 
Blue sky schedule:
* Dec 1 - Final design and PSD original files
* Dec 30 - Options 2 and 3 code complete
* Jan 27 - Option 1 code complete
* Feb 10 (mid-Feb) - QA complete
* Feb 24 - A/B Testing starts
* March 3 - A/B Testing ends
* March 10 - Analysis complete
* March 31 - Launch final design
 
Questions:
* PSD -> CSS/HTML: how long for each option?
* How long for QA for each option?
* Is this worth squeezing in and reaching for if multi-variate testing is not feasible until Q1?
 
== Agenda ==
*Go through all three options verbally.
**Questions about explanations.
**Clarification of Process.
*Discuss constraints.
**Time constraints.
**Resource constraints.
*Feasibility.
 
= PDF =
* Option 1: 1-4 (deciding between a (2) and b (3)) -- page 4 is a continuation of page 3
* Option 2: 5
* Option 3: 6
 
== Process ==
*Get PSDs from TRO
* What is a reasonable timeline for 3 code options being done?
** Which order do we do the designs in, can we break up the QA for each version?
* When does QA period start and end?
*Give code to Blake for multi-variate testing.
*A/B/C test for one week to see which redesign performs best.
*Take down the other two sites.
 
== Option 1 ==
*Page 1 of the psd is the main page.
 
*Search Box
***Searches all languages, in both English name and Native name. Results look like results page, showing both English version and Native version of clickable boxes.
**View All
***Displays current all.html page.
**Map
***Scroll over map, the continents get hot. If you click on a continent, it takes you to that continent's results page.
 
*Results Page
**Sniffs to see which OS system the user is using and display results based on the OS.
**Search Box
***Searches all languages, in both English name and Native name. Results look like results page, showing both English version and Native version of clickable boxes.
**View All
***Displays current all.html page.
 
*Every Continent is broken down into regions.
**Every region is highlighted in orange.
**Current OS show under the version number. You can switch to a different OS by clicking on the Mac or Linux logos, for example.
**Results displayed in alphabetical order (by the english version of the language) but the first language shown is the native version. Os version is also in the box.
**Around each language option is a box that becomes visible when the user scrolls over it. It turns green as it gets hot.  The entire box is clickable. Leads to download.
 
 
 
**The version number of Firefox shows up at the top of each region.
 
 
 
 
 
== Option 2 ==
**Browser detects the OS and displays the detected OS first. Can switch OS listings by clicking on logos.
**People can click on the '+' sign to display all the versions in a region. If you scroll over the actual land masses on the right end of each continent, they highlight blue.
**If the user clicks "view all" they are taken to the current all.html page.
**Now that the user has clicked on Europe, all the languages available in that region are displayed, fist by native name, then eng name. Alphabetized by english name.
**The search tool bar is enabled, search both by eng name and native name of each language.
**Languages are first identified by the native version of the language and then the english version of the language.
**As you scroll down the list, each line is completely highlighted in green. If you click anywhere in the highlighted area, you start downloading FF in that language.
**Separate lists for Beta Versions, Language Packs for each continent.
 
== Option 3 ==
* This page is based on the current all.html page.
**Removed version column.
**First column is native version of language and followed by english version. Alphabetized by english version.
**Search bar
**As you scroll, the whole line gets hot. Have to press text link of version you want to download if you are going to download.
**Broken up into beta versions and language packs.
**Search also enables search by native name or english name.
Lmesa
797

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/161170"

Navigation menu