== Background
Preview for disambiguation pages should be able to display relevant information, including a list of the most common disambiguations
Most lead paragraphs/summary/intro paragraph of disambiguation pages is non-empty and 1 sentence about what the primary article topic. which is actually repeat of the hatnote.
for e.g. i read this hatnote >
{F8574588}
and then the first sentence of disambiguation is
{F8574594}
this is a common pattern in all the cases I have seen so far.
The other prominent use case is this
{F8574597}
here, another page tells what this page is about. it's a twisted joke on content design :)
in most cases finding useful and non-redundant content from disambiguation page is difficult. a generalized approach would be explaining what the link will do as shown in the mockup.
= Recommendation
Use our empty state like page preview to convey that this link is about a page that relates to multiple pages
Thinking: WMF design principle says "Content first"
Here's how it might look. similar format as the empty page previews
{F8550107}
== Acceptance criteria
When a user hovers over a disambiguation page, a page preview should appear including the following elements:
- Text: "This link may refer to multiple pages. The disambiguation page will provide a list of these pages"
- Link: "View disambiguation page"
== Developer notes
We can and should use [the Disambiguator extension's API to detect whether or not the page is a disambiguation page](https://www.mediawiki.org/wiki/Extension:Disambiguator#API_usage).