When we first deployed the help panel, one of our concerns would be overwhelming the help desks with too many questions. After a month in production, this has not happened. Czech Wikipedia gets about 0.7 additional questions per day, and Korean gets about 0.1 additional questions per day.
We have learned from the EditorJourney initial report that 64% of Czech newcomers and 56% of Korean newcomers open an editor on their first day, which means that the rest of them don't see the help panel -- even if they could definitely use some help. We also learned that 42% of Czech newcomers and 28% of Korean newcomers visit a Help or Wikipedia namespace page on their first day.
Given this information, we want to:
**Make the help panel present //in reading mode// on pages in these namespaces, in addition to it being available on all pages in editing mode. We think that the users who will see the help panel in those contexts will most likely be looking for help, and will use the help panel productively:**
* **Help talk**
* **Wikipedia talk**
* **User talk**
**It is also important that we //exclude// Main Page, regardless of the namespace it is in for a given wiki.**
This has implications for our instrumentation that we need to decide how to handle:
* We want to know when the help panel is used in the reading context on these pages.
* The HelpPanel schema currently captures an `editor_interface` field, which would not be applicable here, unless we used that field to store that the user is in reading mode.
* The HelpPanel schema currently captures `page_id` and `page_title`, but doing this in //reading// mode for the Help and Wikipedia namespaces would essentially expand our team's data capture beyond what EditorJourney and EditAttemptStep are doing. It would essentially capture the reading behavior for all newcomers in the Help and Wikipedia spaces for an indefinite amount of time after their account creation. This is probably more data than we want to capture, and perhaps we can obscure page_id and page_title.