This is the first task for the "Focus on help desk" feature: making a call to action button/tab can open a help panel when a page is being edited. Requirements for the feature continue to take shape here based on design explorations from T206715.
When I am editing an article and am unsure about how to proceed, ...
...I want to get help while I am doing the editing task ...
...so that I can more confidently complete the edit.
- Platform: This feature will eventually need to exist for both desktop and mobile. Desktop should be built and deployed first.
- Languages: KO and CS (Growth team's target wikis)
- Target users: Determined by business rules defined on T206716
- Eventlogging: This feature will need to be instrumented with EventLogging for all clicks.
- A/B testing: This feature should be A/B testable. We might want to test these sorts of things:
- Having the feature at all.
- Different call to action text.
- Different configurations of elements in the panel.
- Other considerations:
- We want to allow the presence of the call to action to be configurable by the user through a user preference. When we first deploy the feature, users in the treatment group to have the feature should be able to turn it off. Users who do not have it should be able to turn it on. See T206716 for the details.
- The initial version will not go to anonymous users, but subsequent versions may.
- We should be able to support RTL languages (such as Arabic and Persian).
Proposed feature design + requirements
1. Call to action (to open the help panel)
- Mocks: Invision (clickable) prototype at https://wikimedia.invisionapp.com/share/XSP2H5Z7ZMY#/screens/330825313 (Click/Tap on this task in the contents screen to view the relevant mocks) . NB we are using design B
- Prototype: http://reetssydney.github.io/prototypes/help-pane-v1/index.html
- Notes on the design:
- Floating button/tab in the bottom right of the editing experience. Floating means that it stays in the same place in the window even as the user navigates around.
- It should be shown in all editing experiences, regardless of whether it is visual or source editing, and regardless of whether it is the 2010 or 2017 editor. It should also be shown in the "read-only" editing context for protected pages. (Tracked in T211059: Help panel: implement support for VE and MobileFrontend)
- Whether the button is shown by default for a given user should be able to be configured by the number of edits or number of days the account has. (Tracked in T211117: Help panel: provide ability to vary links by context)
- It should be able to have text and an icon. The visual display may differ on desktop and mobile.
- CTA cannot be dismissed, except by clicking a "cog" to go to user preferences and turn it off. (Tracked in T206716: Help panel: business rules on displaying the feature)
- An additional prompt may be incorporated on first time access that highlights the call to action - either the same pulsing dot used to highlight sections of the VE toolbar, or a tooltip. This will not be included in the initial version.
2. Help panel
- Mocks: Invision (clickable) prototype at https://wikimedia.invisionapp.com/share/XSP2H5Z7ZMY#/screens/330826495 (Click/Tap on this task in the contents screen to view the relevant mocks)
- Notes on the design:
- When the button is clicked, a floating panel should expand up from the button. On mobile, this should cover the full screen.
- Should be closable back to the call-to-action.
- Should be able to display text and links. Text and links should be customizable by individual language wikis. See T209297 for details.
- Per T209297#4747465 - Allow for different text and links depending on the (1) Platform (Mobile/Web) and (2) Editor type (VE or Wikitext) (Tracked in T211117: Help panel: provide ability to vary links by context)
- The preferred implementation is shown on Mock 2B whereby the user should be able to "ask a question" directly from a text-field in the Help panel.