YoutubeVideo node for more than Youtube video links

[epavlova]

Background

The content tree defines a node of type YoutubeVideo which represents a Youtube video link. The node has the following definition:

interface YoutubeVideo extends Node {
	type: "youtube-video"
	url: string
}

The bodyXML representation of a Youtube video link is the following:

<a data-asset-type="video" data-embedded="true" href=""></a>

Example: "Trump’s second term: what will it mean for America and the world?", Jan 2025:

<a data-asset-type=\"video\" data-embedded=\"true\" href=\"https://www.youtube.com/watch?v=Y_uIs_Z9z4w\"></a>

The XHTML representation is more generic, applicable to any video source. Nothing specifies that the video source is YouTube. For that reason, the Specialist content uses these <a data-asset-type="video"...> tags for Vimeo videos as well.

Examples:
"51 for 51: Industry has moved on from ‘boys club mentality’ but there’s more to do", Mar 2025 :

<a data-asset-type=\"video\" data-embedded=\"true\" href=\"https://vimeo.com/1069557147\"></a>

"Spring Statement 2025: Stride says chancellor ‘architect of her own misfortune’", Mar 2025

<a data-asset-type=\"video\" data-embedded=\"true\" href=\"https://vimeo.com/1069657473?share=copy#t=0\"></a>

"‘Paraplanners should not fear for their jobs because of AI’", Jan 2025:

<a data-asset-type=\"video\" data-embedded=\"true\" href=\"https://vimeo.com/1051880732?share=copy#t=0\"></a>

Possible approaches

In order to migrate the Specialist content to the content tree format, there should be Vimeo links representation. One option is for the YoutubeVideo node to be made more generic.

[adgad]

I think it might be better if we add VimeoVideo as a separate thing. Though it might be explicit/verbose in the schema, looking at how YoutubeVideo is rendered the component seems pretty specific:
https://github.com/Financial-Times/cp-content-pipeline/blob/f9deff5227f6f5d3d0dfd5e3eabee6599c86aba5/packages/ui/src/components/content-tree/YoutubeVideo/index.tsx#L7

So I feel like having Youtube + Vimeo as separate content tree nodes will make it easier to have different components

[adgad]

TODO: add VimeoVideo to schema

[umbobabo]

So I feel like having Youtube + Vimeo as separate content tree nodes will make it easier to have different components

I agree, this is usually applicable to any embed.

An alternative could be that we explicitly express the provider/platform/publisher
Something on the line of:

<a data-asset-type=\"video\" data-embedded=\"true\" data-provider="vimeo" href=\"https://vimeo.com/1051880732?share=copy#t=0\"></a>

but then our side we will have a single Video component that may need to support multiple providers. However, that is not particularly hard to handle in React.

[umbobabo]

I believe the decision we make here should also influence the Acast issue here >> and potentially define a strategy for any embed that we may use.

Regarding Acast for instance, we don't have a problem now because it's the only Podcast provider we use, but we may have the same issue that we have with YouTube/Vimeo in the future