Extension:PageTriage

PageTriage is an extension that aims to provide a feature-rich interface for triaging newly-created articles. It is intended to replace the new page patrol core function while adding additional functionality for reviewing, tagging, and improving new articles. It adds a Special:NewPagesFeed page, and a page curation toolbar to new pages for those with the 'patrol' permission. It was developed by the Wikimedia Foundation's engineering>Wikimedia_Features_engineering|Features Engineering team. For additional details see curation>Page Curation|Page Curation.

An important note is that some of the configuration and code is specific to the English-language Wikipedia's workflows and as it's constructed now the extension is pretty much impossible to internationalize. (See T50552.)

Installation
To actually see the extension working:


 * Add a new stub page as an anonymous user.


 * Visit Special:NewPagesFeed

The new page should appear, flagged as "", "", etc. To see the page curation toolbar:


 * Login as a user with the 'sysop' permission, or add a group with the "help>Special:MyLanguage/Help:Patrolled_edits|patrol" permission, and add some user to that group, and login as that user.


 * Visit Special:NewPagesFeed


 * Now you should see a "" button next to the new page.


 * Click this and you should see the page curation toolbar on the new page.

Extension configuration
The extension is based on the 'patrol' right. For more information about configuring patrolling, see .

The following configuration variables can be set from your LocalSettings.php file:


 * $wgPageTriageEnableCurationToolbar: Set to false to disable the 1>Special:MyLanguage/Page Curation#User Experience: Curation Toolbar|curation toolbar (default is true)
 * $wgPageTriageInfiniteScrolling: Whether or not to use infinite scrolling in the new pages feed (default is true)
 * $wgPageTriageNoIndexUnreviewedNewArticles: Set this to true if new, unreviewed articles should be set to noindex. In other words, if they should not be indexed by search engines until they are reviewed. (default is false)
 * $wgPageTriageMaxAge: The age (in days) at which PageTriage allows unreviewed articles to become indexed by search engines (if $wgPageTriageNoIndexUnreviewedNewArticles is true) (default is 90).
 * $wgPageTriageNamespaces: The namespaces that PageTriage is active in. (default is NS_MAIN and NS_USER).

See extension.json for the full list of config variables.

On-wiki configuration
It is possible to configure much of PageTriage on-wiki via the pages <tvar|1> </> and <tvar|2> </>, although the structure of the configuration may change in the future (to better accommodate wikis besides English Wikipedia).

You can get a general idea of how the configuration works by looking at the following:

Both of these files operate in much the same way.

There are two top-level jQuery variables that define the curation templates that are listed in the curation toolbar under the <tvar|1></> (add tags) and <tvar|2></> (nominate for deletion) buttons. These are:

The 'Main' and 'User' refer to the namespace of the page being curated. Each sub-item in the three sets above defines the tabs shown at the left side of the toolbar, and has the following form:

Then the actual templates that are listed are defined under the above  variable. Each deletion template has the following form:

At the moment, some tags must be present:



Example
So, if you don't want to use any of the built-in deletion templates (which can be imported from NewPagesFeed_Templates.xml, by the way) then you can replace them all with a single one by adding the following at the bottom of your <tvar|js> </> page:

Client-side hooks
PageTriage provides a specialized action queue system to allow other scripts and gadgets to integrate with it. This is similar to  except that it uses promises. This is done using the  module. See the comments in the for documentation on how the system works.

The actionQueue module is available after the mw.hook  fires. PageTriage will give the action queue handler an Object with the following data, in addition to other data as noted below:


 * — ID of the page being reviewed.
 * — Title of the page, including namespace.
 * — Username of who is using PageTriage.
 * — Username of the creator of the page.
 * — Whether or not the page is currently or will be marked as reviewed.

Available actions

 * — Fired when the reviewer tags a page for deletion. The data given to the handler also includes:
 * — An object of all the templates added to the page. The keys are the template title, and the values are an object of metadata, including things like the speedy deletion code.
 * — Fired when the review status of a page is changed. Also includes:
 * — The personal message the reviewer added for the creator of the page. This may be blank.
 * — Fired when maintenance tags are added to the page. Also includes:
 * — An array of the titles of all templates that were added to the page.
 * — The personal message the reviewer added for the creator of the page. This may be blank.

Example
To use the action queue, register a function to be ran when an aforementioned action is fired. PageTriage will wait for any asynchronous code to complete before doing anything else, such as refreshing the page. For example, to edit Sandbox after a page has been marked as reviewed, you could use:

API
PageTriage adds 5 API endpoints which can be used:


 * <tvar|stats> </> - Retrieves stats about the number of pages in the queue and the top reviewers
 * <tvar|list> </> - Retrieves the list of pages in the queue and associated metadata
 * <tvar|action> </> - Mark a page as reviewed or unreviewed
 * <tvar|tagging> </> - Add clean-up tags or deletion templates to a page
 * <tvar|template> </> - Internal API for fetching Backbone templates for use in the JS application

To check if a page is marked as reviewed using an API query, you can use.