Websites/Processes/New Website: Difference between revisions

Jump to navigation Jump to search

Websites/Processes/New Website (view source)

Revision as of 16:58, 13 April 2011

2 bytes added ,  13 April 2011
no edit summary
No edit summary
Line 81: Line 81:
{URL}
{URL}
</nowiki>
</nowiki>
== 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 not 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 ==
== Privacy and Legal Ticket ==
Line 237: Line 317:
* Please configure Django tracebacks to be sent to:
* Please configure Django tracebacks to be sent to:
** {email1}, {email2}, {email3}
** {email1}, {email2}, {email3}
</nowiki>
== 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 not 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>
</nowiki>
Ryansnyder
1,241

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/298187"

Navigation menu