Thu, Jan 11
He7d3r awarded a token.
Wed, Jan 10
We can show a tooltip that points to the mode switch button. The tooltip will be shown only when the rich text editor is accessed through the link (but not when switching to it in other ways), and will disappear after a few seconds. The tooltip message can be something along the lines of "Switched to visual editing for the preview. Switch back anytime".
Mon, Jan 8
Another report of this issue.
This issue was reported in this comment.
Fri, Jan 5
I illustrated how the different notifications play together below:
Thu, Jan 4
From my perspective a confirmation dialog will break the fluency of the experience in this context (getting in the way of users that may be already about to search for a specific article to translate). I don't expect we need much accuracy (we are just filling the initial empty state with content that may be connected to the user in some way), so the geolocation cookies seems a good approach.
Wed, Jan 3
I think notifications can be useful in this context. We can use them to inform as well as to encourage users to work on the topics they were once interested in, but forgot to follow though. I'd propose the following approach:
Tue, Jan 2
Fri, Dec 29
I captured some concepts on how to support the translation of an article in this video.
Thu, Dec 28
Tue, Dec 26
Sun, Dec 24
Fri, Dec 22
Thu, Dec 21
Thanks for clarifying, @Petar.petkovic. I know that right now the only CX part that can be accessed by anonymous users are the stats, but I think the approach should be more general and be able to support the scenario where users can use the whole CX anonymously in the same way they edit and create regular articles. Even if that is not possible right now.
Wed, Dec 20
Tue, Dec 19
I don't think we should expose users with an artificial language code to represents all languages. Using the translated version of the word "all" seems more intuitive. That is, in Greek it will display "Όλα", and in Baque it will be "Guztiak". We can do this in both small and larger screens. For small screens it is ok if the text gets cropped with ellipsis if it becomes too long, but checking the translations that seems to be the exception.
Mon, Dec 18
Dec 14 2017
Dec 13 2017
What I was trying to point to is that it may not be that minimal (it requires to figure out what to do with the existing highlighting, when hovering a red row), and it may have side effects in terms of distraction and confusion (e.g., users expecting the whole row to be interactive, items being highlighted as the ser just scrolls down the page, etc.).
Dec 12 2017
Makes sense to me. I updated the description too for the idea not to get lost in the comments.
Dec 11 2017
I also found what may be a related issue: clicking on the checkboxes to select a filter sometimes seems to produce a jump, as illustrated below:
Dec 7 2017
Some comments about the "Show changes on pages linked from/to". I guess that the original proposal (F9140533) was modified to add more precision ("show changes in pages" as opposed to just "). I'm ok with that, but I think there is no need to apply that approach to both the selector and also the options. Links are bidirectional concepts, so just changing to and from may not help much users to intuitively understand what we actually mean, even if capital letters are used.
Dec 6 2017
Deciding on the primary action requires to prioritise some usecases over others. Linking to the affected content was considered as the primary action for simplicity reasons. It does not require the interpretation effort that current diff view requires. The drawback of this approach is that it is less precise: the user needs to figure out at a glance if the description was vandalised (easy), it was improved (not that easy to detect) or some relevant information may have disappeared (harder to detect). We decided to err on the side of less experienced users (not requirign to be able to navigate the diff system) by default and provide what we considered more advanced tools as secondary actions.
Dec 5 2017
Based on the feedback, I reviewed the design to adjust the shape, and propose to use the following:
Dec 1 2017
Nov 30 2017
The general approach to give more space to the language selector sounds good to me. I was not getting suggestions when I checked beta (screenshot below), so I was not able to check it live.
Nov 29 2017
Nov 28 2017
Does it mean that the later two work for you?
Nov 27 2017
I explored some variants for the lightbulb icon. Adjusting the shape of the lightbulb may help to recognition. The rays definitely help to recognition, but they also force the main lightbulb body to be smaller and results in an icon with a higher number of small details compared to most on the collection.
Nov 24 2017
Nov 23 2017
Nov 22 2017
Nov 20 2017
Nov 17 2017
Nov 16 2017
This idea came out of the exploration process for New-Editor-Experiences. It is not clear whether it would be part of the main focus of work for any team yet. But given the relative small scope of the task, I thought it would be worth capturing in a ticket to make it available to a larger audience that may be interested.