About 12-15 people attending. Posting the session notes at https://etherpad.wikimedia.org/p/wmhack2022-devportal here:

• What is this all about?
  • Project overview: https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal
  • Alex, Bryan, Tricia, Sarah, Andre, and more people working on it
• Problem
• Previous past approaches (that didn't take off)
• What we have been doing: Two parts: Portal itself, Key Docs linked
  • Initial interviews with engineering teams
  • Multiple rounds of research and testing with developer audiences
  • Iteration on site structure and content to focus on user goals and tasks (critical user journeys).
  • Implementation of tech stack using Material for MkDocs
    • Fun nuances you could discuss if ppl are interested: this stack gives us the ability to create individual yaml files that represent a key doc and then include it in one or more categories that are then rendered on a page or pages in the dev portal. Flexibility and efficient content reuse, but also some limitations with formatting and design.
  • User testing with final version: worked with WMF Design Research team to recruit test participants from both within and outside of the Movement
    • Results: https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal#User_research_on_final_prototype
• Find all and everything at https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal
• We plan all work in the open: https://phabricator.wikimedia.org/tag/wikimedia-developer-portal/ and https://phabricator.wikimedia.org/tag/key_docs_update_2021-22/
• Check the demo: https://developer-portal.wmcloud.org/
• Demo should go down and site should go live next month (if all goes right)

*Translation system hookups and how to help with translating: https://translatewiki.net/wiki/Translating:WikimediaDeveloperPortal#Translation_statistics

• Once live, still wondering how to make the DevPortal more "known". Because so many places! (but see some tasks on the workboard)
• Current demo version, not final: https://developer-portal.wmcloud.org
• How and where to provide feedback
• Contribution is most needed in the area of improving key docs / landing pages (link to phab board and review checklist, but also note that making doc contributing easier is a goal for FY22-23, maybe give a plug for Tricia's session about docs if it hasn't already happened)

FEEDBACK:

• Being able to translate is great
• "About" should not be under "Get Help" - maybe add an item to the footer?
• Should contributing to the dev portal be under "Contribute"? Website itself vs broader contributing to Wikimedia
• Middle level overview missing how pieces work together, e.g. Wikidata, code, architecture [not technical contributions only, also sysadmin/setup etc]
• Tutorials link does not cover materials needed for some use cases
• Set of additional portals for different target demographics, e.g. Wikimedians, external folks?

More feedback is welcome at https://www.mediawiki.org/wiki/Talk:Developer_Advocacy/Developer_Portal