11 Feb
2010
11 Feb
'10
7:47 p.m.
On 02/11/2010 03:43 AM, Caleb James DeLisle wrote:
The problem:
When a new wiki administrator uses the registration application, they are faced with a
set of fields with
names which are too short to explain what each field is for.
eg:
Boolean field named: "Check Active fields for user authentication"
To a new administrator, this is confusing and it's not apparent where to look for an
explanation.
Proposal:
I would like to add fields with names which are links to descriptions of what those
fields are for.
I can implement this in the "configurable" class which I am working on.
This means XE would have links to xwiki.org but it already does on the dashboard
explanation of tags.
WDYT?
I also believe that this is not a good idea. The wiki should be
self-documented, any interface element should be clear. If a simple name
is not good enough, then a tooltip should provide more information. If
that's still not enough, then there is a Documentation link (to
xwiki.org) at the bottom of the page already, the user should find the
full documentation starting from there.
But this is just the ideal solution. In reality, there are plenty of
places where the short name is not descriptive enough (for example this
check Active field), tooltips are rarely used, and many users complain
that they can't find what they're looking for on xwiki.org. All these
must be improved.
For a start, this field could be renamed to "Require account validation
through email" or something similar. Is that still not suggestive enough?
Then, we need to make the property tooltip work.
Third, we need to reorganize xwiki.org.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/