[Spike] Prepare meeting with content transform team about outcomes of new parser
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	ovasileva
	Mar 12 2024, 12:02 PM

Description

Background

The parser migration is causing some issues within the user interface on desktop T358452: Vector 2022 dynamic table of contents broken on Parsoid and mobile. We should spend some time looking into the issues and discussing potential solutions such as T337286: Gadget API for adding buttons to section titles before bringing them to the content transform team.

User story

As a developer, I want the new parser to work with our user interface, so that we can continue with the migration safely

Requirements

n/a

Design

n/a

Acceptance criteria

Review existing tickets and proposals
Document open questions and suggestions from the team
Schedule a meeting with the content transform team to discuss next steps

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Open	BUG REPORT	matmarex	T358452 Vector 2022 dynamic table of contents broken on Parsoid
		Resolved		ovasileva	T359925 [Spike] Prepare meeting with content transform team about outcomes of new parser

Event Timeline

ovasileva created this task.Mar 12 2024, 12:02 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 12 2024, 12:02 PM

ovasileva triaged this task as High priority.Mar 12 2024, 12:02 PM

ovasileva added a parent task: T358452: Vector 2022 dynamic table of contents broken on Parsoid.

I had an opportunistic chance to talk to @ssastry and @MSantos today about the parser migration and agreed this should be considered Essential work by the web team for Q4.

In terms of timeline, the content transform team are targeting full parser migration on English Wikivoyage and Hebrew Wikivoyage by the end of the fiscal year.

While they can ship to desktop only they and I would prefer not to do that as it may create more work for us on the long run.

With that in mind, I think we should aim to plan this work in April/May to avoid being a blocker for them. My prediction is this should be work for 1-2 engineers on our side for about 2 sprints.

We talked to CT yesterday

ovasileva closed this task as Resolved.Mar 15 2024, 8:39 AM

[Spike] Prepare meeting with content transform team about outcomes of new parserClosed, ResolvedPublicActions