IMHO, summary is clear enough.
Some suggestion :
Full Name (cn)
First Name (givenName)
Last Name (sn)
Preferred Language (preferredLanguage)
Steps to Reproduce:
I assume you actually mean the form where a user can edit their details after they have completed registration (https://identity.mageia.org/user), not the registration form itself (https://identity.mageia.org/register).
I have tried to make this interface relatively generic (as I have a few non-Mageia use cases for this software). For example, we just use a list of attributes to display (which is configurable in the config file).
I would prefer not to go and write a more "static" list with different names.
The first option I considered was to use the attribute description as a mouseover, but then you have descriptions like this:
attributetype ( 184.108.40.206 NAME ( 'givenName' 'gn' )
DESC 'RFC2256: first name(s) for which the entity is known by'
SUP name )
The other option would be to (ab)use the i18n support, make all the attribute names localised, and provide "translations" for the attribute names.
New user form is difficult to understand if you don't know LDAP keywords =>
User details form is difficult to understand if you don't know LDAP attributes
Your assumption is right ; it is the form that's popup _after_ a new user registers to the mageia forum and each time someone logs in.
I understand the _technical_ reasons for the current state of the form but don't forget that this form is used by average users just to register to the forum and they shouldn't be scared by a hardly understandable form. We don't want them to think "Mageia is for geeks, not for me".
(In reply to comment #1)
> I would prefer not to go and write a more "static" list with different names.
Well, I for one would prefer to do so, but in a separate controller and view, to at least keep the generic one available, just in case. But again, I'm not so confortable yet with Catalyst.
Making the form more humane and static is not a bad thing, provided it is done right - and it's not likely to be too specific so far - even though we would need to make it really specific later on.
> The other option would be to (ab)use the i18n support, make all the attribute
> names localised, and provide "translations" for the attribute names.
That was my first option as well, to at least keep the generic list; but I was not so sure how/where to code this into the app.
I would also favor a separate controller/view for that use case, this would be much more flexible for designing the form.
Any news/ changes since 2011-04-18 ?
Do you think this page makes it more clear for average users?
The old Mageia user accounts FAQ button is going to be replaced with a link to the page mentioned above (bug 3674)
I guess so, provided the average user RTFM ;)
Maybe a message like :
"See the FAQ for detailed information on fields"
would be helpful on the form itself.