Please contact Jazmin or Olga to set expectations about timeline and ensure this work gets scheduled.

@Jdlrobson and @LGoto who should be contacted about this extension? As of Today, this the Web team is listed as the maintainers of this component.

Yes web team maintain this extension. Please reach out to @ovasileva to make sure time is allocated to do this work.

The RelatedArticles extension registers a parser function for {{#related|page1|page2}}. That should be supported with Parsoid currently, and the plan (T268144#7950406) is to maintain legacy compatibility for these simple text-in/text-out parser functions (although the legacy API might shift to get rid of the ParserFIrstCallInit hook, but that's an orthogonal issue, T299528).

The main incompatibility I can see is in:

	public static function onFuncRelated( Parser $parser, ...$args ) {
		$parserOutput = $parser->getOutput();
		$relatedPages = $parserOutput->getExtensionData( 'RelatedArticles' );
		if ( !$relatedPages ) {
			$relatedPages = [];
		}

		// Add all the related pages passed by the parser function
		// {{#related:Test with read more|Foo|Bar}}
		foreach ( $args as $relatedPage ) {
			$relatedPages[] = $relatedPage;
		}
		$parserOutput->setExtensionData( 'RelatedArticles', $relatedPages );

		return '';
	}

The use of getExtensionData and setExtensionData in this read-modify-write sort of way is deprecated (T300981) and because Parsoid processes the parser functions invocations independently will currently result in throwing away the data from all but the last invocation of {{#related}}. If there's typically only one invocation per page that might not be immediately obvious.

In any case, the fix is simple: the new-ish ParserOutput::appendExtensionData was added specifically to allow composition of lists of this sort. Switching to use that function should eliminate the Parsoid incompatibility AFAICT.

Do you just need code review/testing for this? If the fix is simple it is something the content transform team plans to post patches for?

In T263772#9381096, @Jdlrobson wrote:

Do you just need code review/testing for this? If the fix is simple it is something the content transform team plans to post patches for?

That's a good question! Ideally we would work in a way that shares knowledges about the Parsoid APIs with everyone involved since Parsoid is expected to be the long-term MW parser.

My idea is to prioritise CTT patching for unmaintained Extensions and support owners to work on their extensions with our review/support. How that sounds to you?

Change #1058236 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):

[mediawiki/extensions/RelatedArticles@master] Use `appendJsConfigVar` to track related page titles

https://gerrit.wikimedia.org/r/1058236

Change #1058236 merged by jenkins-bot:

[mediawiki/extensions/RelatedArticles@master] Use `appendJsConfigVar` to track related page titles

https://gerrit.wikimedia.org/r/1058236

Test Result - Prod

Status: ✅ PASS
Environment: enwikivoyage
OS: macOS Sonoma
Browser: Chrome
Device: MBA
Emulated Device: NA

Test Artifact(s):

Test Steps

Test Case 1: Verify Related Articles Rendering with Parsoid

1. Visit India on Wikivoyage in production.
2. Scroll to the bottom of the page.
3. ✅ AC1: Confirm that more than one related article is rendered.