Page Content Service

The Page Content Service (PCS) is a set of node-based services in Wikimedia production designed to deliver Wikimedia project page content and metadata for modern reading clients. It delivers:


 * 1) Optimized page content for modern clients to provide a full article reading experience
 * 2) A standard structured representation for pages that can be used for display within lists and previews
 * 3) Aggregated common CSS used for styling and theming articles
 * 4) Client logic for page interactions such as changing reading themes, handling references, lazy loading images, and more are provided as a JavaScript interface that clients can execute locally

The PCS delivers content in both HTML and JSON formats. It consolidates data from the Wikipedia, Commons and Wikidata MediaWiki APIs as well as the Parsoid and ORES API.

The service will supersede the mobile-sections endpoint of the Mobile Content Service (MCS). Currently, the PCS services code is part of the MCS Git repo. Eventually those will be separated so they can be deployed separately from MCS.

These services are maintained by the Wikimedia Reading Infrastructure team.

/page/mobile-html
Provides Parsoid HTML with a few key differences:
 * Additions:
 * This includes the addition of a few extra DOM elements to add information, like the page title, Wikidata description, a footer, edit icons to sections and the top of the page, etc…
 * Removals:
 * Navboxes
 * Transformations
 * Reference lists are replaced with placeholders to improve initial load time. When references are needed by the client, they can be retrieved using the JSON API for references, /page/references
 * Images are replaced with elements to improve initial load time. Images are lazy loaded as the user scrolls to them
 * The lead content paragraph is moved above the first infobox
 * Infoboxes are collapsed with an interface to allow users to expand them as they read

Examples: Prod | Beta cluster | Labs | Local RB | Local MCS

/page/summary
The Summary serves two very important purposes: To accomplish number 1, it contains some basic metadata: an image/thumbnail, a description, the first paragraph of the page plain text and HTML form ( and  ), and article language and directionality (RTL or LTR). It's preferable to use the  over   since some complex formulas are better handled with HTML than plain text.
 * 1) It provides the data necessary for the representation of a page within a page/link preview, search results, other lists, etc…
 * 2) It provides basic metadata necessary for clients to make business logic and navigation decisions before displaying a page.

To accomplish number 2, it contains some semantic information on the page, its name space, and various URLs in order for clients to understand the content of the page prior to deciding how to display it.

Additionally, the Summary structure is provided in other APIs (like the feed) that return lists of pages.

Page_Previews/API_Specification

Example URLs: Prod | Beta cluster | Labs | Local RB | Local MCS

For comparison, here is the   request this endpoint replaces: Prod. In the current version  is not used anymore, though. Instead PCS gets more of the information from the respective Parsoid HTML output and does some transformations on that.

/page/media-list
Lists media items shown on a page: images, videos, and audio. This is useful for clients wishing to build a gallery interface for content within a page or for downloading images for offline reading.

Example URLs: Prod | Beta cluster | Labs | Local RB | Local MCS

/page/mobile-html-offline-resources
List of the CSS and JS schemeless URLs for offline resourcing for mobile consumption. The motivation for this endpoint is to let native clients know what other files they would have to download when saving a page for offline without having to parse the page.

Example URLs: Prod | Beta cluster | Labs | Local RB | Local MCS

Example output:

Example URLs: Prod | Beta cluster | Labs | Local RB | Local MCS

Clients
PCS can be used by any WMF or 3rd party client that wants to display page content for reading contexts. As mentioned above the  endpoint is heavily used in other places and already use by the native apps and the web PagePreview feature. has some coupling to the wikimedia-page-library and is somewhat tied to design decisions for the native WMF apps. If needed there could be another HTML endpoint that sits somewhere between Parsoid HTML and.

Within the WMF, the following clients are expected to integrate use of  in 2020:
 * 1) Wikipedia Android App
 * 2) Wikipedia iOS App