* Track: Local Development and onboarding
* Topic: Improving documentation and support channelsOn-wiki documentation & documentation as code: strengths, weaknesses, and compromises
* Location: Azalea room
* Time: Wednesday 2019-11-13 13:30 EST
DWikimedia technical documentation is scattered in various placeslives both on wiki (mediawiki.org, which makes it difficult to find.wikitech.wikimedia.org, There is also a lack of up-to-date and high-level documentationmeta.wikimedia.org, etc) and a lack of inclusiveoff wiki (through the source repository, accessible support channels.https://doc.wikimedia.org/, Figuring out how to solve these issues would be beneficial to all developers,etc). and especially beneficial to onboarding new developers
In this session, we’ll compare the advantages and disadvantages of these two approaches and discuss ways to improve the experience for both.
=Questions to answer and discuss=
On-wiki docs are searchable within a single wiki, but these searches don’t include content from other wikis or from off-wiki docs. How can we improve the discoverability of off-wiki docs?
* Creating on-wiki landing pages that link to off-wiki docs.
* Transcluding off-wiki docs into wiki pages
** Example extension: https://www.mediawiki.org/wiki/Extension:GitHub
** Technical challenges
**Question:***** Update process
* Expanding the reach of search to include content across wikis or across sources
** Code search: https://codesearch.wmflabs.org/search/
= Related Issues =When docs are stored in the same repository as the code they describe, either as separate files, code comments, or generated using a tool, doc updates can be made in the same patch as code updates. In this case, code reviewers should request that patch authors add docs if needed before patches are merged. For docs stored on-wiki, it can be more difficult to keep the docs in sync with code changes. What workflow improvements could be made to make on-wiki docs easier to maintain?
* ...* Linking to applicable wiki pages in code comments
* ...Continuous integration that looks for the patch ID in an edit summary
* Publishing wiki docs with an “open patch” label that can be removed once the patch is merged
While on-wiki docs can take advantage of established translation workflows, translation for off-wiki docs can be challenging to support. What processes or tooling can we put in place to make translation easier for off-wiki docs?
* Example: The generated docs for MediaWiki Action API support localization through https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/master/includes/api/i18n
* Publish guidelines for off-wikis docs wanting to support translation
=Pre-reading for all Participants=
* [add links here[https://www.mediawiki.org/wiki/User:Pavithraes/Sandbox/Technical_documentation_templates_and_suggestions|Technical documentation templates and suggestions]]: Overview of various technical documentation types and their characteristics
* [[https://www.mediawiki.org/wiki/User:Pavithraes/Sandbox/Technical_writer_guide|Technical writer guide]]
* [[https://www.mediawiki.org/wiki/User:SRodlund_(WMF)/Maturity_model_for_MediaWiki_technical_documentation|Maturity model for MediaWiki technical documentation]]
=Notes and Facilitation guidance=
* Bryan Davis (@bd808 )
* Chris Koerner (@CKoerner_WMF)
* Deb Tankersley (@debt)
=Session Style / Format=
* [what type of format will this session be?][[http://www.theworldcafe.com/key-concepts-resources/world-cafe-method/|World Cafe]] discussion and list generation.
The room will be setup with 3 stations, one for each of the Discovery, Creation, and Translation topics. Participants will be divided into 3 groups, one for each station, and rotate through the stations with 10 minutes for each group to discuss each topic. The goal of each group during each rotation should be to generate new ideas related to the station's topic, build on existing ideas left by prior groups, and cluster ideas which are similar in approach. During the final rotation, the goal expands to include producing a high level summary of the ideas generated in all 3 rotations to be used in a 5 minute summary to the whole room in the report back phase.
* Welcome and introduction (10m)
* World Cafe round 1 (10m)
* World Cafe round 2 (10m)
* World Cafe round 3 (10m)
* World Cafe report back (15m)
* Wrap up and next steps (5m)
**Session Leaders** please:
[x] Add more details to this task description.
 Coordinate any pre-event discussions (here on Phab, IRC, email, hangout, etc).
[x] Outline the plan for discussing this topic at the event.
 Optionally, include what this session will //not// try to solve.
 Update this task with summaries of any pre-event discussions.
 Include ways for people not attending to be involved in discussions before the event and afterwards.
Post-event action items: