Websites/Blog: Difference between revisions
< Websites
Jump to navigation
Jump to search
No edit summary |
|||
| Line 7: | Line 7: | ||
Right now, we are managing our blogs through separate instances of WordPress and Tumblr, they have different themes and login processes. The way we have been spreading content and information across various platforms in the past reflects our internal team structure to external audiences. Moving forward, we want our communication to clearly reflect “One Mozilla”: People should be able to get a holistic view of Mozilla, easily and at a single glance. | Right now, we are managing our blogs through separate instances of WordPress and Tumblr, they have different themes and login processes. The way we have been spreading content and information across various platforms in the past reflects our internal team structure to external audiences. Moving forward, we want our communication to clearly reflect “One Mozilla”: People should be able to get a holistic view of Mozilla, easily and at a single glance. | ||
This is why the PR team, Creative, IT and WebDev have been working on consolidating Mozilla's blogging platform. Strategically rolling up Mozilla’s blogs onto a single platform will allow us to direct traffic more effectively and present our brand and our messages to community, press, and users more clearly. Mozilla is growing and we have a large content network that we want to leverage more strategically to fulfill our mission. | This is why the PR team, Creative, IT and WebDev have been working on consolidating Mozilla's blogging platform. Strategically rolling up Mozilla’s blogs onto a single platform will allow us to direct traffic more effectively and present our brand and our messages to community, press, and users more clearly. Mozilla is growing and we have a large content network that we want to leverage more strategically to fulfill our mission.<br> | ||
= Goals = | = Goals = | ||
| Line 17: | Line 17: | ||
*Reduced IT overhead (maintain only one theme) | *Reduced IT overhead (maintain only one theme) | ||
*Reduced security reviews for new channels by maintaining a single theme for all channels in one Wordpress instance<br> | *Reduced security reviews for new channels by maintaining a single theme for all channels in one Wordpress instance<br> | ||
= FAQ = | |||
= Overview = | = Overview = | ||
| Line 32: | Line 34: | ||
= Meeting Notes = | = Meeting Notes = | ||
*Kickoff Meeting [https://etherpad.mozilla.org/blog-consolidation-project-110211 2011-11-02] | *Kickoff Meeting [https://etherpad.mozilla.org/blog-consolidation-project-110211 2011-11-02] | ||
*[[Mozilla.org/Websites/Blog/Meetings/November-8-2011|Status meeting Nov 8]] | *[[Mozilla.org/Websites/Blog/Meetings/November-8-2011|Status meeting Nov 8]] | ||
== Bi-Monthly Meeting Schedule == | == Bi-Monthly Meeting Schedule == | ||
TBD | TBD | ||
= Phases = | = Phases = | ||
'''Tier 1 Rollup:''' | '''Tier 1 Rollup:''' | ||
''(approved)'' | ''(approved)'' | ||
*Future of Firefox, [http://blog.mozilla.com/futurereleases/ (Grace)(blog.mozilla.com/futurereleases] | *Future of Firefox, [http://blog.mozilla.com/futurereleases/ (Grace)(blog.mozilla.com/futurereleases] | ||
*Security, [http://blog.mozilla.com/security/ blog.mozilla.com/security] (Lucas A.) | *Security, [http://blog.mozilla.com/security/ blog.mozilla.com/security] (Lucas A.) | ||
*Privacy, [http://blog.mozilla.com/privacy/ blog.mozilla.com/privacy] (Alex F.) | *Privacy, [http://blog.mozilla.com/privacy/ blog.mozilla.com/privacy] (Alex F.) | ||
*Channels, [http://blog.mozilla.com/channels/ blog.mozilla.com/channels] - merge into Dev News & retire | *Channels, [http://blog.mozilla.com/channels/ blog.mozilla.com/channels] - merge into Dev News & retire | ||
*Identity/User Data, [http://identity.mozilla.com/ identity.mozilla.com] (Ben A.) | *Identity/User Data, [http://identity.mozilla.com/ identity.mozilla.com] (Ben A.) | ||
''(pending)'' | ''(pending)'' | ||
*Apps, coming soon - let's do it right the first time! (Ragavan) | *Apps, coming soon - let's do it right the first time! (Ragavan) | ||
*B2G/Research, coming soon (Andreas) | *B2G/Research, coming soon (Andreas) | ||
| Line 74: | Line 77: | ||
= Related Projects = | = Related Projects = | ||
*[https://wiki.mozilla.org/Websites/Press-Center-Consolidation Press Center en-US & EU Consolidation Project - Q3 2011] | *[https://wiki.mozilla.org/Websites/Press-Center-Consolidation Press Center en-US & EU Consolidation Project - Q3 2011] | ||
*[https://bugzilla.mozilla.org/show_bug.cgi?id=687382 Magazine-like Entry Point for Mozilla Blogosphere] | *[https://bugzilla.mozilla.org/show_bug.cgi?id=687382 Magazine-like Entry Point for Mozilla Blogosphere] | ||
= Retrospective | = Retrospective = | ||
Revision as of 10:33, 17 November 2011
This page contains all of the important details for blog.mozilla.org
Summary & Project Background
Currently, we have more than a dozen official Mozilla Blogs set up on different platforms. This raises several issues: Press, our users and even Mozillians often find it hard to find information they are looking for. The wide pool of channels also makes it difficult for our audiences to identify Mozilla's position on different industry developments.
Right now, we are managing our blogs through separate instances of WordPress and Tumblr, they have different themes and login processes. The way we have been spreading content and information across various platforms in the past reflects our internal team structure to external audiences. Moving forward, we want our communication to clearly reflect “One Mozilla”: People should be able to get a holistic view of Mozilla, easily and at a single glance.
This is why the PR team, Creative, IT and WebDev have been working on consolidating Mozilla's blogging platform. Strategically rolling up Mozilla’s blogs onto a single platform will allow us to direct traffic more effectively and present our brand and our messages to community, press, and users more clearly. Mozilla is growing and we have a large content network that we want to leverage more strategically to fulfill our mission.
Goals
- Organize all official Mozilla channels into a workflow that would allow teams to publish from one blog.mozilla.com, share a taxonomy, theme, url structure
- Enhance seo and domain strength
- Create contextual relationships around content
- Create clear communications to different readers: community, reporters, users
- Reduced IT overhead (maintain only one theme)
- Reduced security reviews for new channels by maintaining a single theme for all channels in one Wordpress instance
FAQ
Overview
- Prod URL: http://www.example.com
- Stage URL: No stage available for blog.mozilla.com at this time
- Code Repo:
- L10N Repo: No l10n at this time
- Code: HTML, PHP, Wordpress
- Product Owner: PR Team; Valerie Ponell
- Dev Team: Group; Person
- IRC Channel: #www and #spinzone on irc.mozilla.com
- Team: Melissa Shapiro, Valerie Ponell, Mike Alexis, Chrissie Brodigan, Jake Maul
Meeting Notes
- Kickoff Meeting 2011-11-02
- Status meeting Nov 8
Bi-Monthly Meeting Schedule
TBD
Phases
Tier 1 Rollup:
(approved)
- Future of Firefox, (Grace)(blog.mozilla.com/futurereleases
- Security, blog.mozilla.com/security (Lucas A.)
- Privacy, blog.mozilla.com/privacy (Alex F.)
- Channels, blog.mozilla.com/channels - merge into Dev News & retire
- Identity/User Data, identity.mozilla.com (Ben A.)
(pending)
- Apps, coming soon - let's do it right the first time! (Ragavan)
- B2G/Research, coming soon (Andreas)
Tier 2 Rollup:
- Executive leadership (Mitchell Baker, Brendan Eich, Gary Kovacs)
- Hacks, hacks.mozilla.org
- Labs, mozillalabs.com / mozillalabs.com/rss
- WebFWD, blog.webfwd.org
Tier 3 Rollup
- Metrics, blog.mozilla.com/metrics
Bugs
- Tracking Bug 699578
Visual Assets
Related Projects
- Press Center en-US & EU Consolidation Project - Q3 2011
- Magazine-like Entry Point for Mozilla Blogosphere