Thu, Jul 18
I'm removing the design tag on this as we have finalized this in terms of what we will ship for V2.
Wed, Jul 17
yes, so this should be moved to the backlog
Meta question that occurred to me during usertesting recently. Is it onboarding to VE or general editing onboarding?
Tue, Jul 16
I drafted a version of the toolbar where the toolbar has a static state. In order to get to this I made the following changes:
+1 thanks for creating this ticket @Esanders
@Esanders - what's the final copy?
Nice catch @Esanders
Mon, Jul 15
+1 (sorry for the delay) this is an obviously better proposal. 🛳 it.
This statement is a very important call-out from @Esanders:
Sat, Jul 13
What flows worked:
- adding a link
- editing a link
- removing a link
The tests are complete. I will follow up by providing a synthesis here.
I just added a few outcomes from the usertesting.com tests
Fri, Jul 12
I had to re-launch the tests because the tests were defaulting to wikitext (not Visual Editor). @Esanders has rectified that issue and have just deployed the tests. They should be done by the weekend.
Thu, Jul 11
I have a draft of my blogpost up on Medium and am waiting for a few folks to review it before posting.
Wed, Jul 10
We went with a minimal version of the implementation for V2.
We should tackle each individual context treatment separately and break them out into individual separate tickets.
The test is up and running on usertesting.com right now.
It should take a few days to get the results in and then I will provide a synthesis after watching them.
We are in a good place with the content.
Everything is already being tested so lets ship this ticket.
Tue, Jul 9
Great, I've asked for a few folks on the editing team to QA the test today before we put it up on usertesting.com to double check that the flows work.
Mon, Jul 8
I drafted a test script for review.
Wed, Jul 3
Here's my latest mockup.
Tue, Jul 2
For a more accurate view of the current design applied to desktop:
Capturing a google chat conversation that @Esanders and I am having regarding desktop implementation of the cards.
I drafted a version of the design document in Google Slides.
I mocked up a version of several applications of the design.
Please drop feedback into the Invision doc.
Mon, Jul 1
Thu, Jun 27
After some more feedback, I have yet another iteration, which now places the publish button up into the toolbar as a primary button. There are several reasons to do this, but my main concern right now is that the icon designs are not 100% unequivocally localizable and therefore this could potentially make publishing more confusing.
👍 or 👎or general thoughts?
In general, I support this change @matmarex. I am wondering does remove link have the same definition as unlink? To me unlink means to detach the existing link but possibly maintaining the intention to re-link, while remove means to go nuclear and complete change it back to plain text. As I write this I'm not even sure if it really makes a difference.
Wed, Jun 26
Related to this, we should make publish flow connected to the upcoming edit card release T225725 so that there aren't two different versions of that final edit summary page depending on if you’re coming from VE or Wikitext editing.
@Esanders I started to take a stab at this work and I actually think that it would be easiest to discuss areas where it is impacting the desktop experience during implementation.
After an initial round of feedback, I took a stab at trying to bring more importance to this moment of publishing to the web. (The fact that the publish was live so quickly has often been described as uncomfortably surprising to Editors). This iteration, I took the button out of the toolbar and moved it into the publish flow as an actionable button (removing the need for an icon). I also used this opportunity to tweak the design of that page.
I took a first pass at a few publish icons. The mockups are here and on Freehand.
Tue, Jun 25
Just chatted with @Esanders about this and we think the best way to approach this is to mock up a desktop view of the card (rather than picking out bit by bit).
Re: the application of the design.
I see this design being easily translatable to other contexts. Here is what it will look like for a citation (also added to freehand). @Esanders has pointed out that this wouldn't be a perfect 1:1 fit for some contexts which don't have a description such as gallery and math. I will work on thinking those through next.
@matmarex thanks for your feedback here re:
I would like us to change the "Unlink" label to "Remove link", because:
@Esanders and I were just discussing T225725 where we have a label input dialog. I mocked this up for the narrow screen size (320px). We realized that when the title bar has buttons multiple actions and a title, it becomes unnecessarily complex. To account for this, we have been exploring the principle that when we have a dialog title, we should be doing icon-only actions. This is what it will look like for us:
@Volker_E and I discussed today that we should ship this as it generally has the appropriate look and feel. In a future iteration, we can then address the excess visual noise.
Mon, Jun 24
Here's another version that I mocked up, removing some of the visual noise:
"Add a link" dialog: we use "Apply Changes" for the confirm button in this flow and "Apply" in others – why are these not consistent throughout?
Fri, Jun 21
+1 I would vote for tweaking that @Volker_E