Websites/Your Web: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 49: Line 49:


= Requirements =
= Requirements =
* Web app that focuses on a visualization of user-generated answers to questions
* These questions can be changed out over time, and all responses are kept even when new questions are added.
* Only one question is featured at a given time. This is the question that appears by default when a user visits
* All responses are text, but users can also upload an image of themselves holding a poster with the text on it as well.
* Design elements: Will use common Mozilla.org design elements and styling.
* Static content: 50 word blurb below the
* Submission form: Response to question, image (optional), user's tag (Developer, Artist, Student, etc.), locale, newsletter opt-in, and privacy checkbox.
* Newsletter: Response submission form has an opt-in to subscribe to the Mozilla & You newsletter.
* Sharing: Users can share their own response on Facebook and Twitter. Users can also share out any response in the visualization on those social networks. May also allow users to share responses via email (see Considerations).
* Localization: All static content will be localized before the site launch. Dynamic, user-generated content may or may not be localized. See the Considerations section above.


= Timing =
= Timing =

Revision as of 17:52, 22 August 2011

This user engagement microsite is for a retention campaign aimed at deepening relationships with Firefox users and educating them about why we make Firefox. The concept is to show examples of how and what people think about the Web, connect that back to why we make Firefox, and then ask users to submit their response to the question. We then showcase submissions in a compelling gallery.

Project bug: bug 667729

Team

  • Product Owner: William R
  • Engagement: Winston (Engagement)
  • TPM: Chris More (TPM)
  • UX: Crystal
  • Designer: Tara
  • Content: Carmen Collins
  • Media: TBD
  • L10N: Stas
  • QA:
  • IT:
  • WebDev:
  • Security:

Information

  • IRC: #yourweb

Considerations

  • Make this web application be generic to the question it is asking so we can use it in the future for other campaigns.
  • All of the answers should be foreign keys to the question ID.
  • Get existing L10N community to do the app's strings.
  • Create 100-200 pre-populated submissions from the Mozilla community.
  • TBD: After the website is live, we would like to have any user of the website to translate the pictures/words and also require Mozilla approvals. This feature may be removed.
  • Which web platform should be used for development? PHP and Django (Playdoh) are the two being considered, and they have tradeoffs for development time and IT resources. If PHP is used, we may want to host this app externally.

Documentation

Meetings

Environments

IRC

Let's collaborate on #yourweb

Bugs

Requirements

  • Web app that focuses on a visualization of user-generated answers to questions
  • These questions can be changed out over time, and all responses are kept even when new questions are added.
  • Only one question is featured at a given time. This is the question that appears by default when a user visits
  • All responses are text, but users can also upload an image of themselves holding a poster with the text on it as well.
  • Design elements: Will use common Mozilla.org design elements and styling.
  • Static content: 50 word blurb below the
  • Submission form: Response to question, image (optional), user's tag (Developer, Artist, Student, etc.), locale, newsletter opt-in, and privacy checkbox.
  • Newsletter: Response submission form has an opt-in to subscribe to the Mozilla & You newsletter.
  • Sharing: Users can share their own response on Facebook and Twitter. Users can also share out any response in the visualization on those social networks. May also allow users to share responses via email (see Considerations).
  • Localization: All static content will be localized before the site launch. Dynamic, user-generated content may or may not be localized. See the Considerations section above.

Timing

  • Live Timeline
  • Project has been on pause for a few weeks while finalizing resources.
  • Late September or early October go live date