Summary of the technical infrastructure activities

Activities	Outputs	Impact
Dashboard Development & Feature Prioritization Define a technical plan, including the prioritization of features based on community input. Possibilities include: Better organization for campaigns and programs. New features for more languages (e.g., authorship highlighting, on-wiki mirroring). Education-specific features (e.g., assignment design wizard, student feedback tool, detailed stats, better search). Run quarterly feedback sessions to refine and improve Dashboard functionality.	A technical implementation plan with a clear prioritization of features. New and improved dashboard features are deployed based on community needs.	More than 50% of affiliates, organizers, and educators feel the dashboard has improved in key areas based on their feedback. 50% of users are using the improved dashboard to present key results to partners.
User Support & Onboarding Set up an effective support system, including office hours, Telegram, and Phabricator. Create and update an onboarding guide for new Dashboard users.	An updated onboarding guide is shared with users. A support system with clear workflows is established.	More than 50% of affiliates, organizers, and educators feel the support system meets their needs. New users can more easily onboard and utilize the Dashboard's features.

Summary of EduWiki Conversation on Tech Infrastructure @ EduWiki Bogota 2025

What adjustments need to be prioritised for the Programs & Events Dashboard to be useful for the educational community? Rank the following features, then add ones of your own:

Support for features like article alerts, authorship highlighting, on-wiki mirroring, and others that are only available for some language Wikipedias.
Better organizing of campaigns and programs so it’s easier to find ones you care about.
Support for creating and maintaining your own Dashboard installation (e.g., dashboard.youraffiliate.org), which contains only your affiliate’s programs and events.
With this option, enable features such as email directly from the Dashboard, in-Dashboard surveys of participants, and a built-in ticketing system.
Better search of the Dashboard
Better education program-specific features (e.g., assignment design wizard, easier use of timeline, easier to create training modules for your program, etc.).
Feedback features for articles (instructors can add feedback within Dashboard)
Better organising for campaigns and programmes
Integration with translation
Features for all languages
Track usage of offline contents, like kiwix repository
Solving encoding issue for other languages.
More Wikidata integration (QID label, subclasses of items).
Set particular category for editathon (eliminate articles beyond the category)
Group work features for students
Wiki Url shortener for dashboard
Rate section of the lesson
Integrate with Copyvio tool
Providing detailed stats and info about the contributions of the participants (how many edits, links, etc)
Update and integrate machine learning models from ORES into lift wing infrastructure.

What forms of capacity building would be best to offer better support for Dashboard users?

We need to provide lots of different opportunities for capacity building around the Dashboard;

Video tutorials
Ways to review retention
In-person training and workshops
PDF tutorials on commons
Zoom meetings in local languages work through the tool (it is already happening and it is useful)

What other key tools do you think should be included in this Technical Infrastructure service the hub hopes to provide (Note: These are likely to be out of scope for Phase 1, but could be added to the technical roadmap)?

Tools for indicating Gen AI was used in the article creation process, tools for making multimedia contributions easier; multimedia tools (making content contribution easier)
Impact visualisation tools
Templates indicated that the article is within the scope of the educational project