Wikimedia blog maintenance/April 2011 overhaul

This page attempts to assess the current situation regarding Wikimedia blogs, and to propose improvements.

Current situation
The Wikimedia blog was created in April 2008; it was presented then as a way to "engage in a less formal discussion, and to bring up the sorts of topics that may not fit in a press release" and "a space to ask questions of the Wikimedia community.

The Wikimedia tech blog was created in March 2009. Its goal stated then was to be "much more technical [...] than the Wikimedia Blog (which covers Foundation issues and news)" and to cover "software updates, server changes, and other such issues".

In practice, though, the line between the content of these two blogs is difficult to draw. Monthly engineering reports, for example, aren't only of interest for a tech audience. Having two blogs also creates redundancy.

Besides, as the Wikimedia Foundation grows, other departments are likely to want dedicated blog sections as well; it's already the case for the Community and the Strategic product departments. Initiatives like India and the Brazil Catalyst Project are likely to follow.

Our current blog setup suffers from some flaws:
 * The current layout gives all posts the same weight, whether they're important announcements or "routine" posts.
 * The current layout makes it difficult to browse posts by topic; categories are underused or abused, and in any case hidden in the sidebar.
 * The theme imitates the Vector skin of MediaWiki, but isn't really adapted to showcase the content of a thematically diverse blog.
 * The coverage is inconsistent, depending on the size & composition of the teams, and willingness to communicate.

Having some sort of separation between departments would help solve some of these issues. However, creating different blogs for each department causes additional issues:
 * Readers need to subscribe to several RSS feeds, or to visit different websites.
 * Posts get duplicated between blogs.
 * Blogs require separate administration and maintenance; accounts have to be created separately.

Fortunately, it's possible to accomplish some separation with a unique blog used well.

Proposed channels

 * highlights / featured
 * technology
 * community
 * chapters / global
 * foundation / "corporate"
 * wikis (signpost, milestones, etc.)

Technical proposal

 * Based on the assessment of the two solutions (WordPress single install vs. WordPress network), the proposed solution is to use a WordPress single install.
 * Channels are implemented as top-level categories.
 * "Routine" posts are published in their dedicated channel, and "important" announcements in the additional "highlights" channel that will give them more visibility.
 * Channels use the same theme; channel-specific changes can be done easily by adding category-specific CSS classes to the  (by adding classes with a filter using the body_class function).
 * Channels are not included in the permalinks structure for performance reasons and because Cool URIs don't change; if a channel needs to be renamed in the future, we don't want to break all the permalinks.
 * Most (sidebar) widgets are common to all channels (basic links, donate button, etc.).
 * Some amount of widget customization can be done but should be left to a minimum to keep a consistent look. For example, links can be selectively displayed according to their link category.

Implementation plan

 * Week #9
 * Guillaume, Jay, Steven: discuss requirements ✅
 * Guillaume: assemble technical proposal based on requirements ✅
 * Jay, Steven: look for sites & features we can use as inspiration
 * Guillaume: get admin rights on the blogs to export the content for the prototype, or get an admin to provide them ✅
 * Guillaume: check how to merge authors ✅
 * Week #10
 * Guillaume: submit technical proposal to Jay & Steven ✅
 * Guillaume: prepare prototype if possible ✅
 * Jay & Steven: comment on proposal; if ok,
 * Guillaume: discuss feasibility with RobH
 * Guillaume: do reality-check with RobLa
 * Guillaume: discuss implementation plan & schedule with RobH
 * Guillaume: check categories on all posts on the Wikimedia blog
 * Week #11
 * Implement?
 * Post away!
 * Merge the tech blog in

Things to keep in mind

 * Small "status" widget, linking to http://status.wikimedia.org and/or short articles about outages; right now the information is scattered around microblogs / short articles on the tech blog (but should interest a very general audience of users)
 * Identica Widget
 * Currently, the Communications team oversees the main blog. This could be scaled to a team of channel curators who would particularly care for their channel (handle moderation, copyedit articles, encourage people to write articles, etc.).