Fri, Nov 16
per conversation with @SBisson @MMiller - for varA, we'll change the styling of the Skip button to make it more obviously a secondary exit action by making the button (1) Frameless and (2) Destructive:
hi @Mholloway - apologies for not being clearer on the original design doc but the idea did not require tracking a "revert rate" per user per se. Rather, once we determine the amount of edits to 'unlock' (let's say it's 20 edits), then when a user makes the 20th edit, we wait for a set time (eg., 48hrs) to see if there is *any* revert activity. If there is not, we will unlock the next task queue.
Thu, Nov 15
– Yes that was the intention. We can repeat the note here that their email won't be disclosed if that helps.
- We discussed whether automatically generated headers are a good idea when the question is automatically posted to the help desk. Here are some of the considerations:
- In @Urbanecm's and @Trizek-WMF's experience, the best help desk question headers contain a summary of the problem, e.g. "How to add a photo to Koala article". That's because a new section header is the edit summary by default, and the edit summary is visible in RecentChanges or Watchlist. So when experienced editors are looking at their feeds, they can tell what the question is about and decide whether to go answer it.
- But on the other hand, it is common for newcomers to give really undescriptive headers, e.g. "Problem" or "Need help", and that is worse than an automatically generated header.
- We talked about whether there would be some hybrid approach in which a newcomer could override the automatic header to provide additional context.
Hmmm, I'd prefer to keep it simple for users posting questions here, since that is part of the rationale for enabling fast and easy question posting. Can we proceed with automatic headers for V1 and monitor the quality of responses?
Another reason for the automatic headers is so that we can call out explicitly to the experienced editors on help desk that it is a question coming from this help pane (and hopefully tailor their responses accordingly with more context).
Yes that's right.
– Not sure if it is needed in the hint text, it is meant to be the same as the 'Create account' field.
(2) There is one interesting case with selection from drop down list. Type 'T' in 'Add more topics' - two options will be presented: 'Technology' and 'Transportation'
Hit 'Enter' - 'Entertainment' will be selected instead:
Wed, Nov 14
FYI this was part of the unresolved items on https://phabricator.wikimedia.org/T165964#4715285
- The design decision on Desktop is for the pane to be an overlay, with users able to scroll content out from behind it (or minimize the help pane) if they decide to return to editing.
- The mobile design is a full screen dialog within the edit mode since there is limited real estate for it to be side-by-side with editing (similar to when they open a template or add a citation on mobile). The benefit is that users do not lose their in-progress edit when they close the help pane.
An initial version of this could just include all Help pages and use the existing search capability to see the number of people who look at suggested answers.
If the user selects "No" (they no longer need help), they will be returned to the default Help pane
What if the page that has been suggested is not what they were looking for? Is the user still in the help pane? If so, will the question (which can sometimes be very long) will be kept somewhere to be posted? If not, what is the end process?
Do you mean if the user selects to view one of the 'suggested answer' links? If they click on suggested answer A, they see the answer open in a new tab so the help pane, edit state and entered query is not lost.
@schoenbaechler - yes on the Android version the image definitely can fit height.
That's a good idea if possible to provide different top 5 links depending on editor context! @MMiller - is this something we want to explore for V1?
Hi @Trizek_WMF - yes, that is one of the open questions on this task. We wanted to capture the proposal first, and discuss feasibility when and if it's decided this makes sense as a later feature to add.
Tue, Nov 13
Just quickly created an icon using the TWN logo since that seems to be the format.
Created in 20x20 and 30x30px in color (their logo colors), grayscale (WMF colors) and mono (single WMF color) to select from depending on what the convention is for showing site logo icons on Echo:
Mon, Nov 12
Oh I was under the impression from the task description that the error is that "the drop down list won't open anymore" after one selection is made? Can @Etonkovidova confirm?
hi @SBisson - I referred to way that the block email field works in Preferences as the expected behavior, whereby the user should be able to select multiple items in the droplist, as well as add their own. Is there some parameter for TagMultiselectWidget that needs to be set for this to work as expected? Or perhaps should the MenuTagMultiselect be used instead?
Sun, Nov 11
Sat, Nov 10
Oh good catch. @SBisson can each link when clicked from the thank you page have a parameter appended to indicate this? Something like ?source=thankspg
Fri, Nov 9
Thu, Nov 8
Tue, Nov 6
hi @Volker_E - here are some proposed updated icons attached. We could potentially try showing this in a toggle select widget instead (like the Left/Right/Center position field above Image type in the screenshot) per ESanders suggestion...
Mon, Nov 5
- Good point and it was a constraint due to my lack of cs and ko context. However, Facebook at least is in there as a site popular in both countries. Similarly, reviewing ZenDesk and Intercom (the company that provides the customer service for Airtable) is intended to capture best 'global' best practices generally.
- For specific cultural comparison I did have a look at a couple of popular Korean sites like Daum, Naver etc and wasn't able to see prominent in-context help (though these are more portals and I may have missed something in translation). The one place that is pretty equivalent was namuwiki but afaik they do not offer in-context help, but rather 'front load' their site with lots of comprehensive help for new editors (getting started guides, links to forums, etc); as well as showing similar links to help at the bottom of pages when editing (but which direct users out of editing).
Fri, Nov 2
hi @MMiller_WMF, @nettrom_WMF - I wrote up some high-level learnings to consider in the ICH design, please feel free to add and comment on the full doc:
Hi @Dbrant (cc @cmadeo) - given there's a fair amount of comments about the unstructured ToC, just wanted to bump this ticket about finishing the visual design items on this task. esp. points 1, 2 and 3.
Thu, Nov 1
hi @MMiller_WMF - see the comparative review deck, I've started iterating on designs based on the some of the main takeaways already but please comment if there's anything particular you want addressed.
Wed, Oct 31
hi @SBisson - still waiting on Legal for the privacy statement link, but note that we've updated the welcomesurvey-question-mentor-info field slightly to the following:
Hi @nettrom_WMF - I agree that looking at how many people complete vs skip the survey and then abandon the site is a good indicator. Other ideas that might be useful consider:
- How many people who skip the survey to go directly to trying to edit a page? (Does not matter if they successfully complete the edit.) This may be a better indicator of whether people don't want to complete the survey than complete abandonment of the site.
- How many people click on "Getting started with editing" links (Tutorial and Help Desk) from within the survey (either on the RHS panel or on the post-submission page) regardless of survey completion?
- What are the activation rates for those users?
- Splits on Activation rates or edit attempts for those who completed the survey based on answers to Q1 & Q2... Would it be interesting to see whether those who originally created an account just to read or didn't know Wikipedia was editable end up trying to an edit after exposure to this survey?
Tue, Oct 30
Fixed as of 2018-10-29 release.
Has been resolved as of 2018-10-29 update.
Mon, Oct 29
@MMiller_WMF - the varA copy is essentially completed, only missing links and OK from Legal. Note that the column for additional information for TranslateWiki is also completed assuming we are going with that option (else it is probably still useful for however we end up translating the text).
hi @MMiller_WMF - I've updated the mocks and description, consider the design and therefore this task completed.
Fri, Oct 26
Hi @revi - to clarify, the topics shown are all just placeholders and don't mean anything, we haven't settled on how these options will be shown yet (that is the subject of T207290)
Apologies that using" enwiki-only topic" was confusing!
Thu, Oct 25
Wed, Oct 24
Revised due-date to allow interested parties time to provide feedback prior to proceeding to Translate Wiki.
Tue, Oct 23
Sounds good @MMiller_WMF. One clarification is that if we use the Process dialog component then mobile will show OOTB as a full screen overlay.