Better UX - explain options better

[echelon]

On every option to mark/set/change give a simple, short, easy explanation of that option which can be understood by every people.

If no easy text is found, remove the option or hide it in "advanced config for nerds".
Users should NEVER let alone on a options with a question mark in their head and in the need of external help.

[zzz]

I assume you're talking about the console? If I'm wrong please fix the category. Please give us a few examples.

[echelon]

Yeah, console.
It was meant more a general information, guide for setting up the pages.
More or less: good UX is, if a button does not need a explanation for the user.
Example: network advanced page. Good to hide it for usual user. Lots of technical term, nearly all need explanations, bad for usual users.
On the advanced: while installing there is a "open port on firewall" text somewhere. Good for I2P, but usual user does not know more about this. Good UX is: hide it! Let advanced people find it on advanced page to setup

echelon

[zzz]

Before we start this, we need some style guide and consistent CSS on how to do it.

Tooltips? Help in the margins? A standard "?" icon next to each that leads to a popup or help page?

Need decisions before we can proceed.

[zzz]

Add a subticket #1766.

[slumlord]

I like the idea of an unobstrusive "?" button that opens a full help page in a new window with relevant explanations. dd-wrt does something like this and I found it helpful.

[sadie]

info tips are useful in the way that they are being used now in the sidebar and console/home page. - for detailing underlying control of the object or menu item. This is helpful for new/ occasional users for navigation of the console. I agree with Ech that if no short easy explanation can be given, hide it.