one approach I just thought of is to test showing the "See also" related links under the paragraph where they first appear, in the form of these cards (that way the links that are elevated are under editor control).

could the spike cover whether there's differential effort in two options, particularly the first screen Justin shared and the one I did (want to keep a focus on a more visual experience that breaks up long text blocks as priority, though I also like the idea of changing link presentation in the article text--current default could certainly also improve a11y by not relying on color alone, but I digress)?

yes! I think the first interaction is basically a simple share button. my thought for what pops up when you select "share" is riffing off what substack does. here's an example:

reference (very lo-fi, not a true mock!) for the story

thanks, @KSarabia-WMF! those are great references. the questions in this learnings section could be helpful to consider too: https://read.chaitime.ai/i/161898756/my-learnings

Resolving as we don't plan to run the enwiki test based on ambassador wiki results

We want to see usage analysis results from https://phabricator.wikimedia.org/T410178 before we pick up these tasks, as they'll be dependent on decisions on which features we take forward to scale and, relatedly, whether we'll build on existing MediaViewer.

talk to Sherry before picking up work here as experiment strategy evolves

chatted with Brooke today and we think this one likely has two points left based on where we landed with requirements above

discussed with @jwang that we won't limit the treatment based on any page attributes, resolving

for the question in the measurement plan GoogleDoc, devs aligned on proposal one, bucketing page length in bytes by orders of magnitude. discussion on Slack: https://wikimedia.slack.com/archives/C08TB64J750/p1763492173335759