Bug 358514

Summary: [UserBase Wiki] Make registration possible to find, fix registration links
Product: www.kde.org Reporter: qubodup
Component: generalAssignee: kde-www mailing-list <kde-www>
Status: REPORTED ---    
Severity: critical    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
URL: http://i.imgur.com/3qGbNOP.png
Latest Commit: Version Fixed In:

Description qubodup 2016-01-25 02:07:49 UTC
1. Two pages link to https://userbase.kde.org/Special:UserLogin/signup which confuses new users who are trying to figure out how to register. The messages need to be changed. Instead they should link to https://userbase.kde.org/index.php?title=Special:OpenIDLogin


Video of one problematic case: https://youtu.be/d2jHIIt_KaI

2. It is impossible to quickly find how to register. Please solve this by editing the skin so that in "PERSONAL TOOLS" instead of "OpenID / Identity login" it says "Register" because it seems an openid/kdeid/whatever login results in the requirement to create a username which is what "registration" is to people. OpenID and "identity" is unknown and makes people think they have to look elsewhere. If you rename it into "Register", then people will quicker realize that they have to read the wall of text below the openid form (by the way, you might want to make the kde identity login the one that is pre-selected and on the left).

Ideally also remove the openid icon. it's confusing. people who like openid will cheer when they go to registration but people who just want to register and have no clue about openid are confused by the icon.

3. If you're at it, you could remove the layout-distrubing language icon and padding from the "English" (language) link. See http://i.imgur.com/3qGbNOP.png for how it could be...

Reproducible: Always

These issues cause you to lose contributions because users can't figure out how to start contributing.
Comment 1 Justin Zobel 2021-03-09 07:26:15 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.