Prioritizing full name vs username in the UX

I just added a site setting that allows you to prioritize full names as opposed to usernames in the UI.

When usernames are prioritized cause the site setting prioritize_username_in_ux is enabled you will see:

In card:

On user page:

In post stream:

If you change it so prioritize_username_in_ux is disabled you will see:

In card:

On user page:

In post stream:

I feel an @ symbol may be worth adding per:

This can be done safely via CSS, leaving it off for now.

Quotes inside the UX still pull in username eg:

We may look at making this switch to be fullname based when the setting is set.

18 Likes

Bug report: If full name is blankish, username is offset and not fully bold

1 Like

eh?

corrected per

Still abusable, but we might as well correct that server side by doing a trim on save that is unicode aware.

3 Likes

That is a can-of-worms to implement, same class as improving quotes. I may get to it, but not for this round.

3 Likes

I believe the username should be shown with @ by the default. It’s a lot less confusing.

And the username should always be visible. Don’t make me think.

4 Likes

At symbol too noisy repeated all over the page. In the user card should suffice.

1 Like