Confirm
583
edits
Changes
Created page with "This page describes a project to modernize publishing on www.mozilla.org == Why does this project matter? == www.mozilla.org contains content owned and maintained by numerou..."
This page describes a project to modernize publishing on www.mozilla.org
== Why does this project matter? ==
www.mozilla.org contains content owned and maintained by numerous teams, including...
* Marketing and engagement content, such as http://www.mozilla.org/en-US/about/
* Policy content, such as http://www.mozilla.org/en-US/privacy/
* Encyclopedic content, such as http://www.mozilla.org/about/forums/
* Product details, such as http://www.mozilla.org/en-US/firefox/23.0/releasenotes/
* Security bulletins, such as http://www.mozilla.org/security/announce/
[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Algxlsc2cLlldDdXMjhsNE92cThIVjRWanp3Ul9vd3c#gid=0 Here is a list] of known, existing '''publishing workflows'''. These publishing workflows are pathways whereby content owners can publish content directly to www.mozilla.org. They are distinct from content that is updated by web engineers in response to a request. In many cases, these workflows are essential: For example, the release and security teams must be empowered to publish releases and security bulletins without engaging a web engineer.
While numerous teams have accountability for content published on www.mozilla.org, the www.mozilla.org product manager (Jennifer Bertsch) and the Web Productions team share ultimate accountability for the coherence, functionality, appearance and efficacy of the website.
In order to allow certain content owners be to publish directly to www.mozilla.org, while maintaining the overall branding and functionality of the website, the Web Productions team will undertake a project to provide a publishing system (or multiple publishing systems) that satisfy content owners' unique needs.
== Team ==
* Product Owners - Jennifer Bertsch, Chris More
* Web Engineers - Paul McLanahan, Josh Mize
* Product Engineer - Justin Crawford
== Code ==
* [http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/ Mozilla.org SVN]
* [http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/ Mozilla.com SVN]
* [https://github.com/mozilla/bedrock/ Bedrock GitHub]
== Contributor Resources ==
== Project Tools ==
* [https://bugzilla.mozilla.org/show_bug.cgi?id=874137 Tracking Bug]
* [https://mozilla.kanbanery.com/projects/35638/board/ Kanban] ([https://mozilla.kanbanery.com/projects/35638/board/?key=e10988e27054b24613dbec481b994669860cf71d Public View])
* [https://groups.google.com/forum/?fromgroups=#!forum/mozilla.dev.mozilla-org Mozilla.org Mailing List]
== Meetings ==
== Why does this project matter? ==
www.mozilla.org contains content owned and maintained by numerous teams, including...
* Marketing and engagement content, such as http://www.mozilla.org/en-US/about/
* Policy content, such as http://www.mozilla.org/en-US/privacy/
* Encyclopedic content, such as http://www.mozilla.org/about/forums/
* Product details, such as http://www.mozilla.org/en-US/firefox/23.0/releasenotes/
* Security bulletins, such as http://www.mozilla.org/security/announce/
[https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Algxlsc2cLlldDdXMjhsNE92cThIVjRWanp3Ul9vd3c#gid=0 Here is a list] of known, existing '''publishing workflows'''. These publishing workflows are pathways whereby content owners can publish content directly to www.mozilla.org. They are distinct from content that is updated by web engineers in response to a request. In many cases, these workflows are essential: For example, the release and security teams must be empowered to publish releases and security bulletins without engaging a web engineer.
While numerous teams have accountability for content published on www.mozilla.org, the www.mozilla.org product manager (Jennifer Bertsch) and the Web Productions team share ultimate accountability for the coherence, functionality, appearance and efficacy of the website.
In order to allow certain content owners be to publish directly to www.mozilla.org, while maintaining the overall branding and functionality of the website, the Web Productions team will undertake a project to provide a publishing system (or multiple publishing systems) that satisfy content owners' unique needs.
== Team ==
* Product Owners - Jennifer Bertsch, Chris More
* Web Engineers - Paul McLanahan, Josh Mize
* Product Engineer - Justin Crawford
== Code ==
* [http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/ Mozilla.org SVN]
* [http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/ Mozilla.com SVN]
* [https://github.com/mozilla/bedrock/ Bedrock GitHub]
== Contributor Resources ==
== Project Tools ==
* [https://bugzilla.mozilla.org/show_bug.cgi?id=874137 Tracking Bug]
* [https://mozilla.kanbanery.com/projects/35638/board/ Kanban] ([https://mozilla.kanbanery.com/projects/35638/board/?key=e10988e27054b24613dbec481b994669860cf71d Public View])
* [https://groups.google.com/forum/?fromgroups=#!forum/mozilla.dev.mozilla-org Mozilla.org Mailing List]
== Meetings ==
