Technical Document Re-working Group/Meetings/2018-02-08
Jump to navigation Jump to search
Technical Document Re-Working Group 2018-02-08
Present: Sarah R., Nick W., Bryan D.
- Interesting new docs design variant seen at https://wikitech.wikimedia.org/wiki/Blubber -
- Results of the MediaWiki API Technical Documentation survey and next steps
- Results going up on MediaWiki
- Thinking about qualitative interviews (what to ask)
- Thinking about demographics. We have information on a small section of experienced API users. If we change our scope (looking for new technical contributors) we will need to identify new types of collaborators and reach out to them to identify their needs
- Technical Engagement / Developer Advocacy -- What kind of technical documentation / documentation can we provide to help potential mentors onboard quickly and to make it easier for new contributors to collaborate
- Next focus area -- Toolforge documentation (starting with the Topviews analysis: https://tools.wmflabs.org/topviews/?project=wikitech.wikimedia.org&platform=all-access&date=2019-01&excludes=Server_admin_log
- My guess from pageviews so far is that the Portal Pages are being visited but not getting clickthroughs (as landing pages). If you look at the topviewed pages under the “wikimedia labs portal” -- these are not pages that link from wikimedia labs portal
- It would be nice to see our users' journeys (how are they getting there, where they are landing, going to, duration of stay, return views, etc…) but this can't be accomplished without compromising privacy. Consider setting up qualitative interviews to talk with users about why they visit ToolForge and how they find their way around.
- [discussed putting note-boxes on the high-traffic pages to potentially interest newcomers. E.g "Newcomer? He