@Daimona thanks for sharing the candidate questions!
@Tania_Sola has also mentioned this as something she'd like to have, but I'm guessing no list will cover all? Although she did explicitly name T359073 and T368574, so I'm wondering if there's a way to do this by linking ERT with another tool? Like adapting this version of LimeSurvey Wikimedia Italy implemented: https://meta.wikimedia.org/wiki/Wikimedia_Italia/LimeSurvey?

I'm fascinated by this thread (thank you for resurfacing this @Quiddity !) I agree with both:

• the workaround being too long (as @Johannes_Richter_WMDE pointed out in T95702#11496544), and
• that adding another button to VE can be confusing (as @Mvolz and @Jdforrester-WMF noted earlier).

I just learned about this project and am interested in how the results of Hackathons could be more visible and linked to similar projects. I'm thinking about {T155846: Reference recommender system} (from @Halfak) and projects like the Guided Article Creation.

FYI I have updated this task to integrate @GFontenelle_WMF's request as well as @EUwandu-WMF's

I looove these mockups @JFernandez-WMF @OBenhmida !
Also, +1 to @Daimona's suggestion – if there are more than 3 events targeting the same article, have you considered a "see all" link or some other way to handle overflow?

I've been following this task with interest, as my PhD research involves enriching Wikipedia citation URLs with metadata (domains, media type, country, etc.). Two ongoing efforts might be relevant to the challenges discussed here.

Notes were taken here: https://etherpad.wikimedia.org/p/Wikimedia_Hackathon_2026_Geodata

Hi @Chinmayee_Mishra @Dactylantha @Oyelola_Victoria @BPiovesan-WMF ! Thank you so much for subscribing to this Phab ticket!
This is a quick note to let you know our session will take place on Sunday at 9:00 AM. I’m aware it’s not the best time, but it would really make me happy to see you there, since this session makes much more sense on the last day of the hackathon. That way, we can gather experiences — especially for those who are attending their first hackathon — about what made them feel most welcome and what barriers they’ve encountered!

Wow @Samwalton9-WMF this is incredible, the daily click volumes are fascinating: doi.org dominating with over 17k clicks, followed closely by nytimes.com (~12.5k) and nih.gov (~7k). It really shows how Wikipedia readers are actively seeking out authoritative sources across academic, news, and government domains.

Hi everyone!

Sources were my bread and butter as an academic librarian, and I can't say how excited I am tsee this step take shape! I’ve been following the task closely and love where it’s headed. Here are a few thoughts I’d love to explore together:

+1 on making categories visible to all mobile users. This fifteen-year-old task represents one of the most significant remaining feature gaps between mobile and desktop Wikipedia—and the evidence suggests it's long overdue for closure.

+1 on adding categories to the app. They're not just useful—they're a proven tool for efficient discovery and deeper engagement.

I would think WMF-regions make more sense because so many organizers work with that logic but if not possible the content translation approach works @Isaac?

I love starting with the low hanging fruits so thank you so much for this list @Isaac!
I'd say we go with the Blogpost and tooltips next.
I think the Blogpost could be a version of the about page so we get two birds with one rock? (Hehe kind of violent Spanish saying).
Also I'd like to link the Meta Page, Phabricator ticket, and Blogpost from the tool as I think it is not always obvious for users that all of these exist.
@Mercyoyelakin let us know if you need help with the tooltip implementation and happy to help with the Diff post draft once you have a skeleton ready 🩻 ✍️

This is a great idea @Isaac, @Mercyoyelakin please let us know if you need help implementing the hierarchical region selector

Hum, I think generic geographic topics make sense, especially since some organizers are looking for region-specific tasks (e.g., LatAm, CEE). With Hubs now available, I'd love to know if this simplifies things for them. What do you think, @Isaac?

Hey @KStoller-WMF thank you so much for looking into this with Growth engineers and also sharing these thoughtful insights!
I loved your suggestion about connecting at the WE1 offsite to plan ahead. I'm wondering if a potential approach could be similar to what you did with the Revise tone experiment. As far as I understood the flow was something like:

I discussed this with @Robertsky, so I’m adding him here for visibility — but Robert, please don’t feel any expectation to take this on. Just a heads-up that the Breaking News tool will be open to anyone who’d like to make adjustments.

I love this, and my request is very similar to this one :)

Echoing @SonjaPerry's excitement here!
And I just realized T401237: Cannot access VisualEditor from mobile browser when Wikipedia app is installed is a related task, and you're addressing this matter with so much care and breadth I can't wait to read your results

I'm new to Phabricator and want to be careful not to break anything. I'm wondering if the following tickets should be tracked here or in T115045: ContentTranslation issues with references (tracking) (I couldn't find them in either list) but they seem to be related to reference issues in the Content Translation tool:

I love this @FNavas-foundation, and as we previously discussed, I can see how this could open up many exciting opportunities. I'll share some below:

In case it is useful: the MediaWiki page @Rmaung pointed out was the first thing that came up for me when I googled "Request Access Superset Wikimedia", so it might be good to update that one too? In any case, I'm super happy to learn about the proper process, so thank you, @Aklapper!

Hi Outreachy community! We have received similar requests in the past, so here's a quick note for all candidates regarding the micro-task, that hopefully helps answer your questions:

Hello everyone! 👋

Hi @Pginer-WMF! Now that the blocker T234323: Adapt Content translation's editor to support section translation on desktop has been resolved, I'd love to know the current status of this excellent feature proposal 💜

Thank you for your prompt response @medelius ! Happy to learn you see value in this <3

Now that visibility configs have been implemented in 1191446, could we focus on implementing the replacement action capability next? This would:

• Directly support the "common typos" use case mentioned by the Telugu community. They shared the following feedback

I hope this question makes sense here 🙂.

Thanks for looking into this @ABorbaWMF ! Just to be precise, I don’t think my request is to disallow deeplinking.
For me, the core issue is that once someone is already in the Wikipedia app, there’s no visible way for them to know about or access VisualEditor (VE). For example:

Hi @Harej ! I'm interested in both the status of this amazing proposal (and if there are any plans of continuing the work for Librarybase as well!)

Wow! I'm so glad this research was requested. Thank you for these valuable insights @nettrom_WMF (and @ifried for flagging it!).

Yaaay, thank you so much for this update @KStoller-WMF - let me know if I can be of any help!

Hi @Pginer-WMF and team!

It seems @Gabinaluz has wrapped up their work—could this help advance the initiative?

Thank you so much @Pablo and @Isaac - I will share the updated code in this task once I get there!

Just to add another reason why we might want this, here's an example of an Event that does have a Dashboard link but was added incorrectly in the wikitext.

Hi team! I was recently participating in Wikimedia Mexico's #JuevesWiki as a volunteer and was made aware that the References Count seems to not be working yet for Spanish.
I added some references to test this article and couldn't see them reflected in the Dashboard. Are there any news on when we might see a change?

Hi everyone! I was wondering if this tool is now named differently? I went to the link (https://tools.wmflabs.org/worklist-tool) and it seems dead

Sorry, I missed your comment @Urbanecm_WMF ! As far as I know ORES-powered revision counting only works where ORES is supported, this is a problem for many languages, and the reason why we thought LiftWing could be an option.
For instance, Spanish, French & other languages references are not being counted in #1Lib1Ref campaigns in the Outreach Dashboard. Fortunately, @Gabinaluz is currently working on solving this issue

Beside the points raised by @Daimona (about people not having an email or disabling notifications) I would like to raise another risk: notifications that go to the spam folder.
Re: crowded design, I actually think the benefits are greater :), and I would even think a little calendar icon would not hurt on the Event Page design @gonyeahialam shared :)

Got it, thank you so much for your help @SLyngshede-WMF !

Hi @SLyngshede-WMF !
Woooow that was weird, if I clicked on reset password using Silvia G, I got no E-mail, but with segt, I did. Any idea why? But yeah, logging in with "Silvia G" did the trick for me, thank you so much!

Gracias again @Gabinaluz <3
And please do let me know if I can serve as a bridge for anything you might need from the Foundation. I usually don't have the answers but know who to ask :)

Hi @klaul!
I'm sorry for the inconveniences! This issue has been reported here and this is why Sam has closed this issue here, to keep working / updating there.
Meanwhile, one solution I'm offering organizers is [[ https://quarry.wmcloud.org/query/79694 | this Query in Quarry ]]where you can get all the edits done with the #1lib1ref hashtag in a given Wikipedia language.
I've added instructions there, but feel free to contact me at silviaegt (at) wikimedia.org if you have any trouble running the Query.

This is excellent news @Gabinaluz, your project will make many librarians and organizers happy! Wishing you all the best for this internship!
From March onwards, who would be best to contact to follow up on the implementation?
This is just to have the most accurate information to share with participants who would like to use the Dashboard for the campaign in May, but if there's also someone they could report potential bugs to that would be nice to know as well :)

Dear team,
The #1Lib1Ref community is so excited about this!
As you can see in the column "Getting data to score" of this feedback board, one of the pain points in the past has been that the Dashboard did not register references for Spanish nor French (and I imagine some other languages)?
We (Gorana Gomirac,Sailesh Patnaik, and I) will be meeting with #1Lib1Ref organizers, and it would be awesome if we could share the good news with them about the advances! Are there any probable dates of when this update will be launched @Gabinaluz ?

Just wanted to see if there are any news on this @Amire80 @jhsoby :)

Dear @SLyngshede-WMF thank you so much for your kind help. The Wikitech link you've sent states that "To reset your password, use idm.wikimedia.org."
I did this an hour ago (11:45 GMT-5) and I tried to log in with my new password two minutes after, 10 min after, and 30 min after. None of this worked. Is there anything else I can do?

Thank you'all for your work on this <3
Good, diverse, crowdfunded & assessable references, is our strongest card in the face of AI/LLM's hallucinations, and I believe as @KStoller-WMF said that this would help to highlight how important references are to the wikis!
Let me know how I can help with specifications.
Just in case it is useful: In the Outreach Dashboard references were also counted via ORES using the features' data (if I'm not mistaken it is under feature.wikitext.revision.ref_tags).
Fortunately this data will also be available via LiftWing

Oh! How does one do closed connections? Sorry @Chicocvenancio, I'm super newbie!

Thank you @Chicocvenancio for reading my question and adding your ideas! Yeah, I just run the code with another Wiki account I have and it went well, so I'm guessing every user gets a limited number of SQL runs?

If possible, I would like to have the editors' data* from each one of the 14 programs of an Outreach Dashboard Campaign ("AfLIA Campaigns")