Content Platform Team
|
MediaWiki Content Platform Team
Build and maintain transformations of wiki content between different formats
|
The Content Platform team manages how all wiki page content is displayed to readers and editors on all devices. Their goal is to support the large number of content formats and types across all languages efficiently and to enable new scenarios for experience teams.
Mission statement
[edit]In short, the Content Platform team deals with content formats and transformations between them.
A bit more specifically,
- We (aim to) provide specifications and guidance for wiki content formats
- We develop transformations between content formats
- We build and maintain content rendering and content transformation infrastructure
- We build tooling to verify content integrity and content migration
Team members
[edit]History
[edit]Prior to May 2015, the MediaWiki Core team was responsible for MediaWiki Core and its Parser, and the Parsoid team was responsible for Parsoid.
In May 2015, the Parsoid team was rebranded as the Parsing team and the Parser and Parsoid were brought under the same roof, with new members temporarily joining in May 2015 and April 2016 before leaving in April 2017 to join the MediaWiki Platform team.
In August of 2021, the Parsing team welcomed members of Maps and Product Infrastructure team to become the Content Transform team.
In July 2026, following the expansion of the MediaWiki Engineering Group, the team became the MediaWiki Content Platform team.
Current Work
[edit]In the 2026-2027 Annual Plan, the Content Platform team will be working on the following three items, under the ST6: Strengthening & Risk Mitigation of the Platform objective:
- ST6.4: By the end of Q3, our platform is able to sustain 20% of page views from logged-in users
- ST6.5: By end of Q3, all WMF wikis use Parsoid for desktop & mobile readviews and metadata
- ST6.6: By the end of Q2, 5 wikis with at least 5% of content pages each are using modules shared via the new cross-wiki collaboration infrastructure
Collaboration
[edit]Engaging with the Content Platform team
[edit]Phabricator
[edit]Anyone outside of the Wikimedia Foundation can get our attention by opening a ticket in Phabricator tagged with Content-Platform-Team. This will make the ticket visible to the team at their weekly triage meeting, where the ticket will be given one of the following dispositions:
- It may be moved to another project the Content Platform team is responsible for.
- It may be moved to the "Later" column on the Content-Platform-Team board, if it is an issue the team is not ready to deal with yet.
- It may have the Content-Platform-Team tag removed, if the team disagrees that the ticket falls under the projects they are responsible for.
Gerrit
[edit]The team maintains a Gerrit review board.
Reviews in code repositories that the team is responsible for should be visible on this board.
This board is, however, a work in progress, and may not encompass all the repository of the team.
To get our attention on a specific review, tag it #ctt-attention.
This will make the review visible to the team, where the review will be given one of the following dispositions:
- It may be attributed to a team member for review
- It may be tagged
#ctt-techforumfor patches that require a team discussion - It may have the
#ctt-attentiontag removed and/or the#ctt-triagedtag added, if the team disagrees that the review falls under the projects they are responsible for.
Slack (Wikimedia Foundation Internal Only)
[edit]Wikimedia Foundation personnel can find us on Slack at #content-platform.
Code repositories that the Content Platform team is either directly responsible for or shares responsibility with other teams
[edit]| Service | Description/Notes |
| Parsoid | PHP library that is used for converting back and forth between wikitext and HTML |
| FeaturedFeeds | Adds syndication feeds of wiki's featured content |
| JsonConfig | Provides a wiki-based JSON configuration system |
| Kartographer | Allows adding maps to pages |
| Kartotherian | Map tile service developed by the Wikimedia Foundation, which itself contains code from Mapbox |
| Language converter | Script & regional term conversion for several languages, e.g. Chinese and Serbian. |
| Linter | Help users find out-dated bits of wikitext to fix them |
| Mathoid | Mathoid is being phased out as part of RESTBase sunsetting (T338429) |
| MobileApp | Serves styles and scripts for use in the Wikimedia native apps |
| Page Content Service | Serves various APIs for rendering page content |
| MultiTitle | Gives the appearance of one page having multiple titles |
| Output Transform | Post processing ParserOutput contents |
| PageAssessments | Stores assessments of pages made by WikiProjects |
| PageImages | Stores information about images representing a page |
| Parser | Issues relating to the wikitext parser, which converts wikitext markup into HTML (including ParserOutput and ParserCache) |
| ParserCache | Responsible for caching the rendered output of a wiki page |
| ParserFunctions | Enhances parser with logical and string functions |
| ParserMigration | Allows users to preview the appearance of articles with the new Parsoid parser |
| Parsoid Integration | Issues relating to MediaWiki's integration with the next-generation Parsoid parser |
| PdfHandler | Handles PDF files like multipage DJVU |
| Proton | Renders PDF versions of Wikipedia articles. |
| Scribunto | Provides a framework for embedding scripting languages into MediaWiki pages |
| TemplateStyles | Allows for loading sanitized CSS stylesheets from a template |
| Wikifeeds | Provides content used in the featured content feeds of the Wikimedia Apps |
| IDLeDOM | Set of PHP interfaces automatically generated from the HTML DOM API, based on a rigorous PHP binding of the WHATWG WebIDL specification |
| RemexHtml | Parser for HTML 5 |
| wikimedia/wikipeg | PEG tokenizer library which we forked from jspeg around 2019 to develop custom / advanced features for our needs |
| Zest | Pure PHP CSS selector library which is a port of the JavaScript zest.js library.
|
See also
[edit]- The Long And Winding Road To Making Parsoid The Default MediaWiki Project: Tech talk from February 2019 (Video, Slides).
- Wikitext, Upcoming changes, Available tools, How you can help?, a presentation by Subbu Sastry, Wikimania Montreal, August 2017.
- Special:PrefixIndex/Content Transform Team - Content Transform team-related pages on this wiki
- Special:PrefixIndex/Parsing - Other content-transform-team related pages on this wiki from the now merged Parsing team
- Special:PrefixIndex/Parsoid - Parsoid-specific pages on this wiki