Avoid targeting YML files in "Learn more" links

[tidoust]

Reviewing the proposal to add a quick lookup to the Baseline landing page in https://github.com/web-platform-dx/web-features/pull/1800 makes me realize that the "Learn more" link is a bit abrupt: it takes me to a YML data file when I would rather have expected to, well, learn more about the feature in a more digestable way.

Since the group also maintains a Web Features explorer, one idea could be to link to the page that describes the feature in the explorer, for example, for appearance, link could be to https://web-platform-dx.github.io/web-features-explorer/features/appearance/ instead of to https://github.com/web-platform-dx/web-features/blob/main/features/appearance.yml

An alternative could be to link to a relevant page on MDN, but not all features have MDN pages.

(cc @captainbrosset)

[atopal]

Yes, that was not the intention. The intention to give more info about Baseline and now that we have a landing page for it, it would link to the landing page.

[captainbrosset]

Linking to the baseline landing page seems like the right default thing to do. I would also suggest making the link customizable via the component API surface. While existing consumers want to link to information about baseline, other future consumers might want to link to places to learn more about that particular feature.

[voxpelli]

If one could link the <h1> (or if its changed as asked in #28) as well that would be nice – my initial reaction was to try clicking the title and thinking I would end up at the MDN page for the feature, then when I found out it wasn't linked I clicked the "Learn more" and experienced this