Wed, May 22
The primary goals of this prototype are to gain insights on the following aspects of features within the Editing interface:
editing and links deleting links. We want to answer the following questions:
I submitted a draft to Communications through the Medium App. Hopefully I will publish this soon.
Tue, May 21
Mon, May 20
Moving to "blocked" until we document feedback and steps for our next iteration (planned for later this week)
Now that it's been a few weeks and we have a prototype up, it occurs to me that this implementation is probably not the direction that we are headed.
We wrote up [[ https://www.mediawiki.org/wiki/User:JKlein_%28WMF%29/guerilla-user-testing/Adding%2BEditingLinks-May2019 | this test ]]for Prague Hackathon, perhaps we can repurpose some of this?
Wed, May 8
These look fantastic @cmadeo
Tue, May 7
Thu, May 2
+1 thanks for writing this up @Esanders - I agree! In my latest round of mockups for Adding/Editing Links and Citations with Mobile Visual Editor I noticed that this is an unnecessarily clunky point in the flow.
I'm drafting this in my sandbox
Wed, May 1
Tue, Apr 30
I updated Invision with the latest wireframes (not final UI) - provide anecdotal/nitpicky feedback there and high-level feedback here.
Thu, Apr 25
This is up - really very very very long time until I shared it.
I just published Report Card: Visual Editing on Wikipedia https://link.medium.com/hZPyJne6aW
Presented the brief at the Board Review and Planning meeting on April 24, 2019 - marking ticket at closed.
Apr 10 2019
Apr 8 2019
Apr 3 2019
Apr 2 2019
Apr 1 2019
Documented the edge case in a separate ticket: T219812
Closing this issue.
Mar 28 2019
+1 to removing excess headings for at least the time being. The main issue with any change of this sort is that it will cause the user to lose their focus when switching from reading to editing modes.
Mar 26 2019
Mar 25 2019
I'm deleting this task because the work should be done over in T211789
*When we implement it, let's test the longest message on the narrowest screen with an ellipsis and then troubleshoot
- +1 to CSS
Mar 23 2019
- Good call on spinner+message reading as one, but practically speaking, they are different elements.
- The text is not bold, it just appears that way due to the contrast with the opacity of the overlay
- I wasn't clear on the value of the ... after the word Loading Editor. Is this a semantic thing that I'm missing?
- I defer to you on CSS vs. gif - I suspect the CSS would decrease loading time and if that's true, +1
- Re: spacing - I was thinking the spacing between the close button and divider and the divider and start of spinner would be the same and then the space between the spinner and text would be 1/3 of that space. In the image below, I've used two gifs( for the close button and spinner) so the sizes aren't 100% accurate
- We should default to what is currently used for close button and text
Mar 22 2019
I've iterated a bit in freehand and here's my latest proposal:
Mar 20 2019
Although this new solution isn't the longterm solution, I think that this patch should be merged as it makes the experience usable. My only caveat here is that we commit towards working on a sustainable solution that we are are satisfied with.
Mar 19 2019
Moving this to Blocked/Waiting because I suspect that the work in T211255 will impact the decisions on this.
moving this to Blocked/Waiting because I suspect that the work in https://phabricator.wikimedia.org/T211255 will impact the decisions on this.
I'm thinking something pretty basic, keep the background color white and the close button on the left to have parody with the actual toolbar. In this instance, I've added the 3 loading dots as well.
Mar 18 2019
Mar 15 2019
I'm done with the ux on this ticket. I will be iterating on the UI in T1181
Handing over for implementation.
Mar 14 2019
Update: After doing a design review, it's clear that option A is the direction that we should take here because:
Mar 13 2019
Thanks @Volker_E - I actually want to take a step back as I was not shooting for feedback on the visual design. The designs below are updated to reflect feedback from others (including @Esanders @matmarex @alexhollender @Nirzar ) The problem that we are solving here is actually about wayfinding so that the Editor stays focused on making her edit. I think that we should iterate on one of these two directions because they do not rely on the look or feel of the toolbar (which we know is going to change in the near future). I've updated the Freehand, and here's a screenshot:
Mar 12 2019
Mar 11 2019
Mar 7 2019
I'm iterating in Freehand, here's the latest round of ideas: