View source for Websites/Processes/New Website

This lists all of the tasks necessary to get a new website started.  After receiving a project from a Product Owner and agreeing to move forward, the Project Manager will execute all of the tasks on this list.

= New Website Process =

* Create a wiki page for this website, if not already available, using the [[Websites/Processes/Website_Template|Website Wiki Template]].
** https://wiki.mozilla.org/Websites/Website_Name
* Create a new [https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=Administration Component in Bugzilla]
* If we are hiring a third party vendor for UX, creative and/or development, please follow the process for [[Websites/Processes/New_Website/Creating_a_SOW|Creating a SOW]].
* Define primary and secondary individuals for [[Websites/Processes/Terminology#Roles|project roles]].
* Create a [[Websites/Processes/New_Website#Github|Github repository]].
* Create the [[Websites/Processes/New_Website#Bugzilla_Tickets|Bugzilla Tickets]] for this project. 
* Schedule the [[Websites/Processes/New_Website#Kickoff_Meeting|Kickoff Meeting]].
* Schedule the [[Websites/Processes/New_Website#Weekly_Meeting|Weekly Meeting]].
* Add site info to [[Websites/Active_List|WhoWorksOnWhat]]
** Place HTTP Auth password (if available) on [https://intranet.mozilla.org/Websites/Stage_Passwords Stage Credentials] page.

== Creative ==
Email John Slater and CC Mike Alexis. The creative team will initiate Copy and Design.

== Bugzilla Tickets ==

Create the following bugs for a new website project:

* Create the [[Websites/Processes/New_Website#Project_Tracking_Ticket|Project Tracking Ticket]].
* Create the [[Websites/Processes/New_Website#Webtrends_Ticket|Webtrends Tickets]].
* Create the [[Websites/Processes/New_Website#Goals_and_Measurements_Ticket|Goals and Measurements Ticket]].
* Create the [[Websites/Processes/New_Website#End_of_Life_Ticket|End of Life Ticket]].
* Create the [[WebAppSec/Security_Review_Request|Security Ticket]].
* Create the [[Websites/Processes/New_Website#Privacy_and_Legal_Ticket|Privacy and Legal Ticket]].
* Create the [[Websites/Processes/New_Website#Stage_Server_Ticket|Stage Server Ticket]].
* Create the [[Websites/Processes/New_Website#Production_Server_Ticket|Production Server Ticket]].
* Create the [[Websites/Processes/Tickets/Mailing_List|Mailing List Ticket]] for long (>2 month) projects.

== Github ==

Create a Github repository for this project.

* Create Github repository at https://github.com/mozilla/app_name
* Create Github lib repository at https://github.com/mozilla/app_name-lib (when applicable).
* Grant access to repositories to team members.
* Make public repository unless it's a secret project
** For private repos Give IT, l10n, and other teams access 

== Kickoff Meeting ==
Schedule a kickoff meeting to bring the people defined as having roles to help prepare this website for launch.

Text to attach to the meeting details for the kickoff meeting:

 <nowiki>
 A new website project has been started.  You have been identified as a core
 member who will help bring this website to fruition.  The details: 

 Where:
 {Room}; +1-800-707-2533, pin 369, x.{Extension}

 Driver:
 {Name}

 Project Title:
 {Title}

 Elevator Pitch:
 {Text}

 Estimated Launch Date:
 {Date}

 The wiki page describing this project:
 {URL}

 The tracking bug for this project:
 {URL}
 </nowiki>

== Weekly Meeting ==
Schedule a weekly meeting to bring the people defined as having roles to help prepare this website for launch.

Text to attach to the meeting details for the weekly meeting:

 <nowiki>
This is a weekly meeting to drive the development of {Website Name} though its launch. You have been identified as a core member who will help bring this website to fruition.  The details: 

 Where:
 {Room}; +1-800-707-2533, pin 369, x.{Extension}

 Driver:
 {Name}

 Meeting Agenda:
 {URL}

 The wiki page describing this project:
 {URL}

 The tracking bug for this project:
 {URL}
</nowiki>

== Project Tracking Ticket ==

This ticket is required for all new websites. Workflow is as follows

* Submit the project through [https://intranet.mozilla.org/webtools/ the project initiation form] 
** this will create the bugzilla tracking ticket, assigned to Mike Alexis.

The form includes the following fields. Product owner should provide as much detail as possible. 

Team members:
*IT
*Product/Driver (you?)
*l10n
*Marketing 
*QA
*Security
*Webdev
*Other

Overview

Dependencies
*legal
*security (infra and/or client)
*analytics
*finance/payments
*app
*other

Assumptions

Deliverables

The Web production team will review bugzilla ticket and schedule a meeting to discuss requirements, scope and timeline.

== Webtrends Ticket ==

This ticket is required for all new websites.

* Create a new [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites Bugzilla ticket].
* Make this bug a dependency for the tracking bug for this website's launch.
* Assign the bug to the Developer.

Title:
 <nowiki>Add Webtrends Tracking for {Website Name}</nowiki>

Body:
 <nowiki>
Add Webtrends Tracking code to this website per the instructions in:
https://intranet.mozilla.org/Webanalytics#Track_a_New_Domain
</nowiki>

== Goals and Measurements Ticket ==

This ticket is required for all new websites.

* Create a new [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites Bugzilla ticket].
* Make this bug a dependency for the tracking bug for this website's launch.
* Assign the bug to the Product Owner.

Title:
 <nowiki>Define Goals and Measurements for {Website Name}</nowiki>

Body:
 <nowiki>
Before this campaign launches, let's document how we will measure the
campaign.

Create a wiki page to document these numbers at:
http://wiki.mozilla.org/Websites/Website_Name/Goals

Please record:
* What are the goals for this campaign?
* How do we plan to measure this campaign?
** Which goals will be measured in Webtrends?
** Which goals need to have a stats area in the app's admin panel?
*** Create tickets for stats area in admin panel as needed
* How will we determine whether this campaign was a success?
* When do we need to schedule a post-mortem for this project?

Each of these goals should be measurable.  Provide a start date and an end date by which to measure each goal.  Each goal will need to have a documented way of how of that data will be tracked and measured.  

Starting numbers that will be maintained externally (Twitter followers, Facebook fans, etc.) must be recorded before the site launches.
</nowiki>

== End of Life Ticket ==

This ticket is only required for websites that have a known end of life, such as a marketing campaign.

* Create a new [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=website-archive.mozilla.org&rep_platform=All&op_sys=All Bugzilla ticket].
* Make this bug a dependency for the tracking bug for this website's launch.
* Assign the bug to the Product Owner.

Title:
 <nowiki>Document End of Life Plan for {Website Name}</nowiki>

Body:
 <nowiki>
Before this campaign launches, let's document the end of life plans.

Create a wiki page to document these numbers at:
http://wiki.mozilla.org/Websites/{Website_Name}/End_Of_Life

Please record:
* When will the campaign end?
* When is the estimated date that we will retire this website?
* What are the privacy concerns for this website?
* Identify where are we collecting and storing:
** Name
** Email address
** IP Address
</nowiki>


== Privacy and Legal Ticket ==

This ticket is required for all new websites.

* Create a new [https://bugzilla.mozilla.org/enter_bug.cgi?product=Legal&format=legal Bugzilla ticket].
* Make this bug a dependency for the tracking bug for this website's launch.
* Assign this bug to the Legal contact.

Title:
 <nowiki>Perform Privacy and Legal Review for {Website Name}.</nowiki>

Body:
 <nowiki>
This is a placeholder for the privacy and legal review of {Website Name}.

Current site documentation is available at:
{Wiki Page}
</nowiki>

== Security Ticket ==

This ticket is required for all new websites.

* Perform the actions listed in [[WebAppSec/Security_Review_Request#Infrasec_Security_Review_Request|Security Review Request]] ticket.
* Make this bug a dependency for the tracking bug for this website's launch.

Title:
 <nowiki>Perform Security Review for {Website Name}.</nowiki>

Body:
* Enter items in [[WebAppSec/Security_Review_Request#Infrasec_Security_Review_Request|Security Review Request]].

== Stage Server Ticket ==

This ticket is required for all new websites.

* Create a new [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&format=it_request Bugzilla ticket].
* Make this bug a dependency for the tracking bug for this website's launch.
* Do not assign this bug to anyone.
* Add the push time <nowiki>[2011-12-31 10:00AM]</nowiki> to the Whiteboard, if known.
* Copy the following text into the ticket and update accordingly.

Title:
 <nowiki>Create Stage Instance for {Website Name}.</nowiki>


Body:
 <nowiki>
(This is a placeholder to create a dev/stage instance for this project.)

Please create a {dev|stage} instance for {Website Name}.

== Date Needed By ==
* 2011/01/01

== Language ==
* Language: Python
* Framework: Django
* Base: Playdoh

== URL ==
* Production URL: {URL}
* Stage URL: {URL}

== HTTP Auth ==
* HTTP Auth is required to access this site.
* Please record username / password in this ticket.
 
== HTTP / HTTPS ==
* Both HTTP and HTTPS are required this site.

== Code Repository ==
* Github Repo: {URL}
* Github Vendor Repo: {URL}
** Setup Github to auto-update every 5 minutes.
* SVN Localization Repo: {URL}
** Setup SVN to auto-update every 15 minutes.

== Database ==
* This site requires a MySQL database.

== Other Services ==
* Note Any other dependencies and to look in settings_local.py-dist.
** Responsys
** Memcache

== Settings ==
* cp settings_local.py-dist settings_local.py
* Update settings values accordingly.
* Set DEBUG to False in settings_local.py.

== Cron ==
* bin/update_site.py -e stage
** frequency?

== Tracebacks ==
* Please configure Django tracebacks to be sent to:
** {email1}, {email2}, {email3}
</nowiki>

== Production Server Ticket ==

This ticket is required for all new websites.

* Create a new [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&format=it_request Bugzilla ticket].
* Make this bug a dependency for the tracking bug for this website's launch.
* Do not assign this bug to anyone.
* Add the push time <nowiki>[2011-12-31 10:00AM]</nowiki> to the Whiteboard, if known.
* Add the push to the IT Calendar in Zimbra, linking back to this ticket.
* Copy the following text into the ticket and update accordingly.

Title:
 <nowiki>Create Production Instance for {Website Name}</nowiki>

Body:
 <nowiki>
(This is a placeholder to create a production instance for this project.)

Please create a production instance for {Website Name}.

== Date Needed By ==
* 2011/01/01

== Language ==
* Language: Python
* Framework: Django

== URL ==
* Production URL: {URL}

== HTTP / HTTPS ==
* Both HTTP and HTTPS are required this site.

== VPN ==
* The /admin section should be accessible only via SSL VPN.

== Code Repository ==
* Github Repo: {URL}
* Github Vendor Repo: {URL}
* SVN Localization Repo: {URL}

== Database ==
* This site requires a MySQL database.

== Settings ==
* cp settings_local.py-dist settings_local.py
* Update settings values accordingly.
* Set DEBUG to False in settings_local.py.

== Cron ==
* bin/update_site.py -e prod
** frequency?

== Tracebacks ==
* Please configure Django tracebacks to be sent to:
** {email1}, {email2}, {email3}
</nowiki>