Bug #10990
Redesign 'Help' Button in the Greeter
50%
Description
Nobody clicked on the help button [?] and the only person who felt like he needed help, looked for it and didn’t find it. It needs to be redesigned.
Files
Subtasks
History
#1 Updated by SpencerOne 2016-01-24 23:17:25
‘Help’ is unique in comparison to the rest of the Tails Greeter dialog, because, when the rest of the dialog cannot be understood, the ‘Help’ button should be. Due to this uniqueness, any language is un(der)clear and can not fulfill the intended function.
OPTIONS - In order of preference.
• An icon/symbol that communicates ‘Help’ across all languages.
• An icon/symbol that communicates ‘Help’ to most languages.
• An icon/symbol that communicates ‘Help’ in one language and translated into others with locale auto-detect.
Considerations: Is time accessible before Tor starts syncing the local clock? If so, how can time accurately predict glyph type in highly cultured areas where many different written languages are used? Also, is auto-detect a privacy issue?
ICONS - May be stand-alone, underscored, circled, or decorated in any novel way.
Help - Help
! - Exclaim
i - Information
? - Question
?! - Alert
‘!?! - Really Though’ The ’’ prevents ghosting.
+ - Red Cross
These are all Latin-based and do not clearly communicate “Help” to cultures unfamiliar with Latin; therefore, they will not help :)
U+1F631 - Screaming Face Emoji
This is not culturally limited but also not clearly actionable.
LOCATION - In no particular order.
• Action Bar - Already full; could become cluttered.
• Welcome Text - Would most likely require text to communicate.
• Each Section - Difficult to locate, per feedback.
• At the end - Not locally contextualized to relevant section.
FEEDBACK - From everybody.
Nobody clicked on the help button [?] and the only person who felt like he needed help, looked for it and didn’t find it. It needs to be redesigned.
‘Help’ proposal [is no good] as it makes it impossible to find the help link if you don’t know the word “help” in English.
CONCERN - Some conflicting logic.
If the destination of the ‘Help’ button, whatever the symbol, is text-based documentation, how is that experience handled, given the feedback regarding the lack of universality of English, or Latin-based languages in general?
#2 Updated by SpencerOne 2016-01-24 23:20:22
We should use one of these or decide that there is something better.
It would be nice to have some kawaii instead, though; this will need some thinking.
#3 Updated by sajolida 2016-02-09 10:45:12
I like Help.Icon.png. I has more contrast and is probably more readable than the current one.
#4 Updated by SpencerOne 2016-02-16 20:11:40
- File Greeter.Help.Single.Icon.png added
I think I agree on the icon vs the text.
However, if people don’t know what each section is, then localized icons aren’t as useful. We might benefit from a single location with an icon (attached), given that people that need the help are having difficulties understanding the entire interface.
What to do about the text-based destination of such links? Seems like a hole in the bucket problem.
#5 Updated by sajolida 2016-02-20 18:23:59
- Assignee changed from SpencerOne to alant
It seems like we agree on the resolution of this ticket which was about redesigning a more visible help button. Alan should now move on the implementation. I’m fine with repurposing this ticket, so I’m assigning it to him.
Now, if I understand correctly, your concern now is about where to put such buttons and what ressources to put to (and maybe how the ressources is displayed to the user). I think these are very valid points but out-of-scope here.
Maybe create another ticket about how many help buttons we want on the current design and what kind of ressources they should point to?
#6 Updated by SpencerOne 2016-02-22 17:53:47
The emphasis on ‘redesigning’ is unclear.
>
> sajolida:
> create another ticket
>
The ‘Help’ button includes the context in which it exists and the associated characteristics such as composition, color, and so on.
Some of the logic used to recommend a button redesign conflicts with the destination of the button, and should be considered inclusively.
Maybe a master ‘Help’ button ticket to manage the individual aspects of the ‘Help’ button redesign might more appropriately fit into the way Tails manages tickets. What do you think?
#7 Updated by sajolida 2016-07-15 12:35:11
Did we try using /usr/share/icons/gnome/scalable/status/dialog-question-symbolic.svg for that?
#8 Updated by sajolida 2016-07-15 12:44:48
- File question.svg added
I’m not sure the diamond shape is suitable here and Spencer draw one with a round background which looks good. So here is a vector version based on the question mark from dialog-question-symbolic.svg.
I’m also surprised not to find many (or any) of these in the GNOME interfaces and to have to reinvent this ourselves. Nevermind, but then we should at least use it consistently without all our custom software (Greeter, Tails Server, Tails Installer, etc.) because this way it will gain some more recognition by our users as something specific to Tails; and hopefully well documented and worth reading :)
I don’t know what kind of file people writing code need. So please tell me more. Do you want SVG? PNG? colors? size?
#9 Updated by SpencerOne 2016-07-18 16:38:19
I dig the softness of the bottom of the hangar.
Save .png files, too, so downloads aren’t required XD
#10 Updated by Anonymous 2018-01-19 17:36:23
- Subject changed from Redesign 'Help' Button to Redesign 'Help' Button in the Greeter
#11 Updated by Anonymous 2018-01-19 17:36:34
- related to
Feature #11471: 'Help' button hover state added
#12 Updated by sajolida 2019-01-22 19:19:55
- Status changed from In Progress to Resolved
- Assignee deleted (
alant)
I think we did this already…
#13 Updated by intrigeri 2020-04-15 06:01:55
- Affected tool changed from Greeter to Welcome Screen