Page MenuHomePhabricator

What should we do for ProofreadPage content models
Closed, ResolvedPublic


Session title

What should we do for ProofreadPage content models?

Main topic

Handling wiki content beyond plaintext

Type of activity

Unconference session


=== The problem ===
ProofreadPage, a MediaWiki extension that is intensively used on Wikisource, manages two specific content models:
* Page: pages that powers the proofreading interface that are an extension of regular Wikitext pages and composed of 3 connected wikitext blobs. e.g.
* Index: pages that stores metadata about a book and its proofreading (author, table of contents, mapping between scan file pages and book pages...). e.g.

These two models are currently stored as wikitext matching a specific format (for Page: pages the first and third wikitext blobs are serialized inside of <noinclude> and for Index: pages, the content is inside of a template serialization), mostly because of historical reasons.

What could be done in order to improve storage of these contents?

=== Expected outcome ===
Have a plan of migration of these content models to something more healthy (Wikibase for a part of Index: pages content?).

=== Current status of the discussion ===
* ContentHandler interface have already been implemented for Page: pages content
* modifications have been done to Parsoid in order to allow proper handling of this kind of contents (but Page: pages are not yet cleanly supported by Parsoid):

=== Links ===

== Proposed by ==

== Preferred group size ==

== Any supplies that you would need to run the session ==

== Interested attendees (sign up below) ==

# Tpt
# Add your name here

Event Timeline

wondering if we have a session owner for this topic yet?

To maintain the consistency, please consider referring to the template of the following task description:

To the facilitator of this session: We have updated the unconference page with more instructions and faqs. Please review it in detail before the summit: If there are any questions or confusions, please ask! If your session gets a spot on the schedule, we would like you to read the session guidelines in detail: We would also then expect you to recruit Note-taker(s) 2(min) and 3 (max), Remote Moderator, and Advocate (optional) on the spot before the beginning of your session. Instructions about each role player's task are outlined in the guidelines. The physical version of the role cards will be available in all the session rooms! See you at the summit! :)

Old session. Let's close this task