Wikipedia:Wikipedia Signpost/Newsroom/Content guidance

Recent research
A summary of academic studies done on Wikimedia or with Wikimedia in mind published both indenpendently as the Wikimedia Research Newsletter and as a monthly column in the Signpost. The venture's meta page maintains a searchable archive of issues. You can see previous editions [ here].


 * A todo list of academic publications for this section is maintained in form of an Etherpad that is updated monthly, mostly based on the @WikiResearch Twitter feed
 * Wikimedia Research Showcase (monthly presentations)
 * meta:Research:Projects (directory of research projects on Meta-wiki)
 * WMF's own research projects

Featured content
The "Featured content" section seeks to report on recently featured content on the English Wikipedia. This is the lightest of the regular sections and thus also carries the least serious tone, as its goal is to allow readers to marvel at recent advancements in core content on the English Wikipedia in a visually appealing, experiential way. You can see previous editions [ here].

Other resources include:
 * WP:GO is by far the most useful resource, setting out all promotions in convenient weekly logs.
 * Featured article candidates/Featured log
 * Featured article review/archive
 * Featured list candidates/Featured log
 * Featured list removal candidates/log
 * Featured portal candidates/Featured log
 * Featured topic candidates/Featured log
 * Featured picture candidates/July-2024

Arbitration report
The "Arbitration report" covers ongoing or recently concluded arbitration cases on the English Wikipedia as well as general news related to the functions or functioning of the Arbitration Committee—the latter is especially true where these do not warrant coverage in "News and notes", which has a more project-wide focus. Written as much as possible from the perspective of an unbiased observer, this report summarizes case developments, responses, and impact (what a decision means; what insights it gives into the values the Arbitration Committee holds; how the decision might directly affect the community) for the readers. The aim is to make readers aware of and allow them to understand complex arbitration-related proceedings that they might not otherwise have any discourse with, allowing them to come to their own view regarding arbitration matter. The "Arbitration report" rarely include images but does carry infographics from time to time. The report will generally touch on all open cases and all other announcements made by the committee during the month. The exact presentation of the report is largely dependent on its author and the nature of the news in any particular month.

Historically, the "Arbitration report" has been the most controversial of The Signpost's regular reports. This is largely due to the difficulties of finding wordings that will both satisfy all parties in a case and allow the readers to make informed decisions about them. The traditional compromise on this is issue is to offer a report that may not reflect all parties' preferred presentation of event, but which is nonetheless objective and meaningful. Even achieving this lesser goal (sifting fact from fiction) is a time-intensive business, and so users mentioned in the report are now asked beforehand if they would like to submit factual corrections to a piece via the comments section of the formative article. Since a purely factual "Arbitration Report" can be prone to insensitivity, this early involvement also helps to inject a minimum of warmth back into the report. Arbitration cases are stressful and the report recognises that; for example, quotations are only ever sourced to reflect an editor's considered opinion more accurately, and never to cherry-pick divisive words said in anger. You can see previous editions [ here].

Technology report
The third and last of the three "essential" monthly Signpost sections, the "Technology report" covers news and developments in the technical platforms used by the Wikimedia project. This includes bug fixes, new features in MediaWiki software, and changes in details regarding the operation of Wikimedia sites (including downtimes when they occur). Also within its remit are developments that do not affect Wikimedians themselves, but affect either other MediaWiki users or Wikimedia re-users, including database dump configuration, Semantic MediaWiki, and data mining technologies, amongst other things. Although the report aims to cover such matters for a general audience, sometimes all readers that will be interested in a news item will already be familiar with certain technical concepts, allowing for such context to be skipped (this mainly relates to "In brief" items). In general, two major stories precede an extended "In brief" section that particularly focuses on recent bug fixes.

A list of news resources for the "Technology report" to draw from is again available at the Resources page. You can see previous editions [ here].

The report also republishes items from the Meta-Wiki effort Tech News.


 * Server admin log
 * Recently fixed bugs
 * Wikimedia Technical blog
 * Wikitech-l mailing list
 * Village pump (technical)
 * de:WP:NEU (technical "Project news" page on the German Wikipedia, useful for finding (links to) newsworthy bugs)
 * https://www.wikimediastatus.net/ (recent outages and performance issues)
 * Wikimedia Foundation Grafana (status dashboards)
 * Software deployments

Discussion report
The "Discussion report" aims to provide "a summary of the most significant ongoing discussions and polls of community-wide relevance". In the past "community" was more narrowly defined as "English Wikipedia community", but this need not be the case, and more recent reports should strive to be cosmopolitan in nature. Topics under the purview of the report include requests for comment, village pump discussions, Meta discussions, proposed changes to the Manual of Style, and other such proceedings. When this section is not in regular rotation items of particular significance are absorbed into the regular reports instead, particularly the "Technology report" and "News and notes". Objectivity and impartiality are maintained at all times, although, in common with these two reports, quotations can be used to bring in particularly salient points, even when those are not (in themselves) necessarily representative of a viewpoint. You can see previous editions [ here].


 * Requests for comment
 * Village pump
 * Centralized discussion

Traffic report
The "Traffic report" section reports on the most popular articles on Wikipedia during the latest publication period, serving as a guided commentary on what was hot and what was not with the readership. As with the "Featured content" section the "Traffic report", serving as a curated list, generally has a lighter tone compared to the rest of the publication. This section is written in collaboration with the Top 25 Report. You can see previous editions [ here].

News from the WMF
The Wikimedia Foundation no longer publishes a blog. Our magazine column has been renamed News from the WMF.

The Foundation has created a WordPress website which combines appeals for donations, profiles of staff members, and articles written by the staff on diverse topics, and news about various Wikimedia projects and spin-offs. If The Signpost editors feel some content is interesting enough and topically relevant enough to our readers to be republished, they will do so and may add their own comments; much of our reporting is taken from the News section of the website. It is important to note that The Signpost is nonetheless a fully independent publication, and so the choice as to what to publish and even whether or not to publish is an independent decision entirely at the discretion of the editor(s)-in-chief. You can see previous editions [ here].

Essay
Wikipedia contains hundreds if not thousands of essays written by editors. Some essays are even referred to during various discussions regarding policies and practices. Some of these are widely accepted. Other essays take on a lighter view of topics. Essays are republished in The Signpost to draw attention to the contributions of the writers. You can see previous editions [ here].

Irregular features
These features are currently published with less regularity but still appear at times. Interested in reviving them? Let us know.

Forum
Intended for frank discussion and sharing of opinions between Wikipedians. Similar to an RFC in many ways, though less formal and on a topic that requires more exposition. Discussion is meant to be open-ended discussion instead of a !vote support/oppose type of discussion. You can see previous editions [ here].

From the Archives
A reprint of an earlier article in The Signpost that may remind users and bring to the attention of new users a topic that is still relevant today and/or which may support or complement a topic under one of the other rubrics. Usually selected by the editorial team but also on suggestions of any editors. You can see previous editions [ here].

Humour
There aren't many places on Wikipedia where snide remarks, silliness, sarcasm and irony are appropriate, but in the Humour section such content is welcome. It can also present editorial commentary – framed in a light, non-confrontational manner. Adds a pleasing, more 'magazine' touch to The Signpost and all editors are invited to make suggestions on content. You can see previous editions [ here].


 * Unusual articles
 * Category:Humorous Wikipedia essays
 * Category:Wikipedia cabal humor
 * Silly Things
 * Yet more Best of BJAODN
 * Uncyclopedia:How To Be Funny And Not Just Stupid

In Focus
Usually a submission from a Wikipedia editor or group of editors that focuses on a current specific feature or process of Wikipedia, the Wikimedia Foundation, or concern of the editors that does not fit into Op-Ed, Special Report, or any other regular rubric. You can see previous editions [ here].

Interview
Interviews are preceded by a succinct introduction. Whilst an amount of fact-checking is advisable, respondents are generally taken at their word. The report is accompanied by images. WikiProjects are rarely featured more than once, but when they are the reports are spaced at least a year apart, if not more. You can see previous editions [ here].

On the Bright Side
Generally a 'feel good' story. Comes as a bit of relief among all the doom and gloom that The Signpost sadly has to report! You can see previous editions [ here].

Opinion
An idea or perception not necessarily based on fact, sources, or knowledge. Usually expressed by one or several editors and is generally more openly subjective and opinionated. It is considered worthy of publication at the discretion of the Editor-in-Chief but is not necessarily endorsed by The Signpost. You can see previous editions [ here].

This often helps:

Serendipity
An interesting or anecdotal essay or report of human or general interest. Adds a pleasing, more 'magazine' touch to The Signpost and is often illustrated. Submissions are accepted at the discretion of the E-in-C. You can see previous editions [ here].

Special Report
Usually a detailed report on the implications a recent major policy or technnical change that will affect the processes of Wikipedia and the way editors will work and contribute. You can see previous editions [ here].

Tips and Tricks
Tips and Tricks is a general editing advice column written by experienced editors. Suggestions for a topic, or offers of advice, are welcome. You can see previous editions [ here].

WikiProject report
Each "WikiProject report" selects a WikiProject (or other long-term collaboration on the English Wikipedia) and attempts to inform Signpost readers about the project's work, achievements, and problems from the perspective of an interview with its active participants. This report is coordinated at the WikiProject desk and is also published on an irregular basis. It is generally deemed acceptable to edit the words of the respondent(s) as one might edit a quotation—i.e., to fix spelling, grammar and punctuation only. You can see previous editions [ here].


 * List of previously published interviews (reverse chronological order)
 * Directory of WikiProjects (by topic)
 * Category for WikiProjects (by topic; subdivisions for collaborations, inactive projects, etc)
 * Prefix Index for WikiProjects (alphabetical; every page starting with "WikiProject")


 * Most active projects by watchers of project's page
 * Most active projects by edits to project's talk page
 * Call for interviews template
 * Sample message for inviting interview responses

Obituary
Obituaries are meant to honor and celebrate the dead; they should be solemn and compassionate. Typically, we can use entries from WP:Deceased Wikipedians, with some light copyediting where appropriate. In general, if there is some information missing from the DW entry, which we find and put in the Signpost obituary, it's just as well to go back to the DW page and add this information there as well (and vice versa).

Each issue, it is condign to check the current year's list of deceased Wikipedians for new entries.

Note that, since we often don't know people's real names (and few people bother to include "tell the folks on Wikipedia" in their will or instructions), some time can elapse between a death and an entry's addition to the memorial list. This means that, while new entries tend to show up at the bottom of the list, they often show up elsewhere: the easiest way to see if there have been recent additions is to check the. It also means that it's useful to check previous years' entries as well. You can see previous Signpost obituaries [ here].

Useful links (current year, last year, and previous):
 * Deceased Wikipedians/2024
 * Deceased Wikipedians/
 * Deceased Wikipedians/

Special columns
The Signpost also publishes special columns covering topics in greater depth and length than the formats of the standard sections allow. The two most common such features (and those of most interest to most contributing writers' pieces) are Op-eds and Special reports. Submitted stories are subject to the approval of the editor-in-chief,, and may be published under other headings, such as Community view, Forum, or In focus. We also occasionally publish Book reviews.

All proposals and submissions are handled at the submissions desk. If you have an idea that doesn't fit neatly into this framework, don't hesitate to address us on our user talk pages, by email, or as a last resort, on the general Signpost talk page.

In many cases particular features or sections of features are part of a series discussion a particular topic; these articles are cataloged as series and generally make use of the {{Wikipedia Signpost/Series}} template.

We also occasionally publish rarer features under the following headings:
 * Galleries are purely photographic sections containing featured and other high-quality images in a curated, topical form. This is also currently an internal feature, though based on the feedback we receive we may open it to public submissions in the future.
 * Interviews are handled at the interviews desk. This is an internal desk meant primarily for our regular writers, as interviews of the quality publishable in The Signpost are never incidental in nature. As such the interview desk does not currently have a submission mechanism—to propose an interview leave us feedback on our talk page instead.
 * From the editor(s) postings generally communicating changes behind-the-scenes in operations at The Signpost. A catalog of these communications is available here.
 * Cobwebs (or perhaps "web-cobs"?): That is not dead which can eternal lie, and with strange aeons even death may die. A (hopefully) infrequent feature for lost articles, hidden drafts, and other deleted nonsense found in the nearly twenty years worth of Signpost pages.

Dispatches
Dispatches were handled at the featured content dispatch workshop. Dispatches are topical articles on en-wiki's various featured article procedures and vetting processes. Like the reviews desk the dispatches workshop has mostly lain dormant in recent years, in this case due to The Signpost's increasing shift towards coverage of the Wikimedia movement in general as opposed to elements of our home wiki's specific structure. Such submissions are now solicited via the special desk.

Education report
The Education desk was a short-lived feature which published a few articles in 2012. Its functions were split off from those of "News and notes" but have now been reabsorbed.

Tutorials
Tutorials were publications, coordinated at the tutorial desk and all published in 2008, which provided how-to information on editing Wikipedia (Though semantically these publications were coordinated at the tutorial page and not the tutorial  per se, the page in question is essentially what we would term a "desk" today—the publication of tutorials simply precedes this organizational definition. As it is currently used "series" refers to something else).

This is now considered to be outside The Signpost's scope. Given their age, much of what these articles espouse is no longer applicable or relevant today, and though The Signpost does not mark past content as explicitly historical these publications should nonetheless be read with caution. Users seeking help should refer instead to the wiki's various Help pages.

The Tips and Tricks columns are a spiritual success to these.

WikiWorld
WikiWorld was, as described in its first publication:

Publication ended in late 2008. Though there were calls for a spiritual continuation, The Signpost has never carried comics since. Until now!

A spiritual successor can be found in the CommonsComix column.

From the editor(s)
From time to time the editor(s) of The Signpost wish to communicate information about the publication itself to the audience; in such cases that months's edition of The Signpost also carries a special notice generally titled "From the editors".

Errata
Contributors make every reasonable efforts to make sure they "get their facts right" (the editor-in-chief bears a similar level responsibility for putting out an error-free edition) but as with any other time-budgeted publication they are not expected to be infallible. Contributors should endeavor to avoid putting out material they know to be wrong or misleading. Despite this relatively high quality bar, The Signpost would not be where it is today without the efforts of hundreds of editors who have made their own, smaller contributions, and these are always welcomed.

Major contributors should generally watchlist articles to which they have contributed in order to note changes and comments made, and respond where possible. Where an error is discovered, minor corrections are usually made to the article directly; major corrections may require an accompanying editor's note at the bottom of the page. Post-publishing updates are almost never done unless they would be extremely confusing to a reader, and even then we prefer to leave the content intact. For example, if a linked article is deleted shortly after publication, leave the sentence intact but add an editor's note after the sentence. Post-publication spelling corrections are also allowed, though post-publication copy-editing, which undermines an article's impression of quality, is not. = Publication process =

Publication
Template:Signpost/Deadline contains the anticipated writing and publishing deadlines for the upcoming issue. It is transcluded in various other pages, such as the Wikipedia Signpost/Newsroom.

Script
As of May 2023, most of the publishing process is automated by a user script, see User:JPxG/SPS.js (forked from User:Evad37/SPS).

On-wiki tasks that are not (yet) automated via this script:
 * Update the deadline template: Enter the anticipated publication time of the next issue at Template:Signpost/Deadline (20:00 UTC on the first and third Sunday of each month, as of July 2023)

If there is a problem with the automated process, follow the steps in the section below to publish manually.

Manual off-wiki tasks
The script does all the on-wiki publishing tasks, including local and global mass-messaging. Tasks that still need to be completed manually by the Outreach Managers are:
 * Announce the new issue on WikimediaAnnounce-L, using the pre-generated output below for copy & paste. Send from the  account. When composing the message in Gmail, click the   icon to remove HTML formatting before sending. (WikimediaAnnounce-l will automatically forward every message to Wikimedia-L, so do not send directly to Wikimedia-L, unless there is a forwarding error.) Check here and here to ensure that the messages have been posted.
 * Post to social media: Tweet about the new issue, linking, for example, to https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/Archives/ as landing page. Bridges have been set up to automatically forward tweets to the WikiSignpost Facebook page and Mastodon feed.

The Signpost – –

Single-page view

https://en.wikipedia.org/wiki/Wikipedia:Signpost/Single

https://facebook.com/wikisignpost

https://twitter.com/wikisignpost

https://wikis.world/@WikiSignpost

Manual process
Handle the actual "publishing" tasks in the following order; it should avoid the necessity of having to purge each individual article to update the footer.
 * 1) Create an issue contents page (at Wikipedia:Wikipedia Signpost/YYYY-MM-DD, e.g. this Wednesday: Wikipedia Signpost/). It should be in the same format as Wikipedia Signpost/2016-12-22 (The numbers in the second parameter, the "story numbers," determine the order of the stories in talkpage notifications). If there is a note from the editor, make that story #0, so it is at the top of the list. (It will have different formatting, so only use "0" for important announcements). The sample page shows the "standard order," but it's fine to adjust it to reflect importance. Add the new issue date to each line. Copy the section titles from the draft header template on each section. When you first save the page, all the links will be red until you complete later steps.
 * 2) Move each section to a subpage of Wikipedia:Wikipedia_Signpost/YYYY-MM-DD. When you move each one, in the page title, replace "/Next issue/" with "/YYYY-MM-DD/" (with the actual date numbers).
 * 3) *Make sure each section has a standard name (e.g., "News and notes", not "News") so that the links to previous issues work.
 * 4) *Untick the "Move associated talk page" option (the talk pages should only contain the "please use the newsroom" notice).
 * 5) *If you're an admin or page mover, untick "Leave a redirect behind". If you're not, ask an admin to delete the pages you leave behind (at some point in the next few hours; not mission-critical for publication).
 * 6) *Optional for now: Purge the "issue contents" page created in step #1, and the links should all turn blue.
 * 7) Double-check that the footer exists at the bottom of each section. If it's not there, add the following line:   The YYYY-MM-DD in this code should be replaced with the previous issue in which that section ran.
 * 8) Change Wikipedia Signpost/Templates/Issue to the date of publication, and update Volume #  and Issue #. Write an edit summary that notifies readers, via watchlists, that you are publishing a new issue; e.g. "Publishing new edition."
 * 9) Edit main page, starting with the generic skeleton. Ensure there are no redlinks by removing pages that are not part of the current issue, and manually add irregular content sections. Copying titles and blurbs is tedious without scripts.
 * 10) Create a new single-page edition by copying this code:   to the subsequent redlink you'll see: Wikipedia Signpost/Single/.
 * 11) Create archive page by adding   in the format.
 * 12) Remove "draft" templates from the headers of the pages (this goes from  ).
 * 13) Purge the cache of Wikipedia Signpost/Templates/Issue, Wikipedia Signpost ,  Wikipedia Signpost/Single, this issue's archive page  and this page (the last for pre-generated output to copy/pastes farther down)
 * 14) Announce the new issue on WikimediaAnnounce-L, using the pre-generated output above for copy & paste. Send from the   account. When composing the message in Gmail, click the   icon to remove HTML formatting before sending. (WikimediaAnnounce-l will automatically forward every message to Wikimedia-L, so do not send directly to Wikimedia-L, unless there is a forwarding error.) Check here and here to ensure that the messages have been posted.
 * 15) Post the Signpost on the talkpages of subscribers. You must be an admin or mass message sender to do this.
 * &rarr; See the collapsed section below for instructions and the message wikitext

Additionally:
 * 1) Tweet about the new issue, linking, for example, to https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/Archives/  as landing page. Post to our Facebook page as well. (Note, this will automatically forward to Twitter; we should perhaps disconnect them, if we are going to be diligently posting to both sites.)
 * 2) Post the Signpost on talk pages of subscribers on other projects, using Global message delivery. The subscribe message is loaded into m:Special:MassMessage for automatic delivery; you can use the pre-generated output below for copy & paste. Only users on the access list can initiate a bot run (Meta admins can add themselves).
 * 3) Update the archive overview for the current year at Wikipedia Signpost/Archives/2024, by copying the date above (which will be older) and updating the issue number and date.
 * 4) Cleanup the newsroom: Reset the article status table on the Newsroom by following the instructions in the hidden comments.
 * 5) Leave a note under Notes to thank this week's contributors and to announce any important upcoming news and any issues that have arisen with publication.
 * 6) Find the previous instance of each section, and add a link to the current edition's section. Here is an example edit, where the previous Traffic Report is updated to add a "next Traffic Report" link. Keep in mind, not all sections run in every edition; so in some cases, this will mean going back two, three, or more editions.

Send from Special:MassMessage using the following details.

Page or category containing list of pages to leave a message on: Wikipedia:Wikipedia Signpost/Subscribe

Subject of the message (also used as the edit summary):

< pre style="white-space: pre-wrap;"> The Signpost: < /pre>

Page to be sent as a message:

Section of the page:

Body of the message:

< pre style="white-space: pre-wrap;">  * Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) < /pre>

(The formatted output should look something like this)

Send from meta:Special:MassMessage using these details:

Page or category containing list of pages to leave a message on: Global message delivery/Targets/Signpost

Subject of the message (also used as the edit summary):

< pre style="white-space: pre-wrap;"> The Signpost: < /pre>

Page to be sent as a message:

Section of the page:

Body of the message:

< pre style="white-space: pre-wrap;">  News, reports and features from the English Wikipedia's newspaper Read this Signpost in full &middot; Single-page &middot; Unsubscribe &middot; Global message delivery

< /pre>