Page Content Service

The Page Content Service (PCS) is a set of services designed to deliver page content and metadata for modern reading clients. It delivers:
 * 1) Optimized page content for modern clients to provide a highly polished full article reading experience
 * 2) A standard structured representation for pages that can be used for display within lists and previews
 * 3) Additional metadata about a page that can be used for navigation purposes, business logic, or constructing ancillary views in native code (like the table of contents)
 * 4) Aggregated common CSS used for styling articles
 * 5) Business logic as JS that clients can execute locally

Some additional features are:
 * Consolidates client logic for manipulating and styling page content on the server and executes it reducing code maintenance and technical debt for clients
 * Consolidates data from disparate services into a single purpose-built service for displaying page content

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.

Compatibility HTML
An API for delivering HTML with editing markup removed compatible with reading use cases.This reduces the size of the payload making it more suitable for devices with slower or intermittent network connections. This endpoint is currently private and not cached

Content HTML
Same as above but optimized DOM that is purpose built for delivering "just the content" and with additional style modifications used in modern experiences. This includes the addition content like the page title, lead image, wikidata description, a footer, etc…

It also removes the references section(s) from the end of articles, which can be retrieved separately using the References API.

This API is designed to be used with the JSON endpoints below to build a modern client experience.

Summary
The Summary serves two very important purposes: To accomplish number 1, it contains some basic metadata, an image, a description, and the first paragraph of the page plain text and HTML form.
 * 1) It provides the data necessary for the representation of a page within a preview, search results, other lists, etc…
 * 2) It provides the data 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, it's 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.

API Design details (BTW, should we move this to Page Content Service/Summary?)

Metadata
The Metadata API returns data needed for updating the chrome around a page, like the edit icon, and for displaying ancillary views like the table of contents and "other languages" that the page is available in.

Media
Lists media items shown on a page: images, videos, and audio along with licensing information. This is useful for clients wishing to build a gallery interface for content within a page.

More details

Clients
The PCS can be used by any WMF or 3rd party client that wants to display page content for reading contexts.

Within the WMF, the following clients are expected to integrate use of the PCS in 2018:
 * Wikipedia iOS App
 * WIkipedia Android App