This page contains all of the important details for content.mozilla.org.

Project Description

This project will create a partner-facing Website for Mozilla's Content Services group. It will:

Cast the value proposition for Tiles products to potential partners
Generate and automatically collect leads
Showcase Mozilla Content Services products to industry and community observers

Project Purpose & Details

Content Services is a partner-facing, revenue generating business unit. Our product is seen by 100s of millions of Firefox users, we have existing channels to communicate with these users. We do not have a distinct venue for communicating with potential partners, explaining the benefits of Tiles and being contactable.

Project Brief

Key Objectives Generate, qualify and automate sales leads.

Target Audience Primary audience is our target advertising brand, and these are marketing decision makers at

Web services
Web publishers
eCommerce vendors

Secondary audience is the ad agency that works on behalf of our target brand Tertiary audience is the Mozilla community

Market Insights The problem that we are solving for is understanding of the Tiles value proposition and a “what to do” if you are interested in Tiles. That means:

Why would I want to buy a Tile?
What is the process and requirements for buying a Tile?
What is the next step?

Anyone arriving at the site has awareness of the product. What they lack is a reason to purchase.

The problems our product solves are:

Need to reach a large scale audience quickly
Need to reach a new targeted audience
Need to re-engage current users

NOTE: Market research on these customer problems is ongoing.

Audience think/do/feel Before the customer has visited this site they have awareness of the product - at least of the URL content.mozilla.org. After visiting this site, the customer will know if this product is aimed at them, the effort involved to buy a Tile, and how to proceed.

Tone

The Tone should be in line with Mozilla corporate partner communications:

https://www.mozilla.org/en-US/firefox/partners/
https://www.mozilla.org/en-US/about/partnerships/
https://mobilepartners.mozilla.org/
This site will not have a different / distinct voice.

Content Strategy & Requirements

The site is relatively straightforwards: it does not impact other pages
It will need to host relatively static content.
The site should not use Flash, and will conform to all Mozilla privacy requirements.
The site will require some copy-editing, and should be localised after launch into German and French.
The site will require at least two video assets.
The site will require a contact form which should be integrated with or instance of Salesforce.

Other Considerations

This is the start of Content Services go-to-market and we will be both adding social proof and new product in the coming year. The site must, therefore, be relatively easy to update, specially the value proposition and customer success story spaces.

User Stories

Pending

Project Information

Communications Channel(s)

IRC, Basecamp, or other communications method TBD in negotiation with project team

Team members (RASCI)

TBD in negotiation with project team. R: TBD A: Patrick Finch is deemed approver. S: Content Services product management and BD (Kevin Ghim, Sean Bohan, Justin Terry) C: Business and legal affairs content owner (Geoff Piper) I: Content Services, Mozilla non-Content Services BD

Notes & Meetings Hub

How to contribute

To help test and localise, please contact Patrick Finch

Website Information

Code name: Content.Mozilla.Org
Prod URL: http://content.mozilla.org
Dev URL: http://example-dev.allizom.org/
Stage URL: http://example-stage.allizom.org/
Code Repo: https://github.com/mozilla/example
L10N Repo: https://svn.mozilla.org/projects/l10n-misc/trunk/example/locale/
Code: Language / Framework

Team

The primary and secondary contacts for each role of this project:

Product owner - {Name}
TPM - {Name}
Web Project Manager - {Name}
Developers - {Name}
L10N - {Name}
Designer - {Name}
IT - {Name}
QA - {Name}
UX - {Name}
Security - {Name}
Legal - {Name}

Websites/Content Services Site

Contents