Page Content Service

The Page Content Service (PCS) is a set of microservices to deliver page content in HTML and/or JSON for reading use cases that will be used in the mobile website, iOS app and Android app. These services are maintained by the Wikimedia_Reading_Infrastructure_team.

The service is based on Parsoid output and 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.

Reading Compatibility HTML
An API for delivering HTML with additional markup for reading use cases.

Content HTML
Same as above but optimized DOM that is purpose built for delivering "just the content" of the page while reducing payload size. This API is designed to be used with the JSON APIS 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.

Media
Lists media items shown on a page: images, videos. Maybe in the future also audio and other media types.