Design/UX #14884
closed
Added by Colin McDonald about 3 years ago.
Updated almost 3 years ago.
Category name:
Public Portfolio
Description
During the team meeting on Friday, we discussed whether the pronouns we added to profiles in #13347 should be publicly displayed by default, and whether we should (and can technically) add a toggle to change this.
I've added everyone from that prior ticket as a watcher here, and I'm assigning this to Boone for now, as knowing what's possible from a tech standpoint might help guide our conversation/decisions here. In #13347 we tied a lot of the display to one Wordpress display filter -- is it as easy as a toggle that targets that filter, at least for public display? Do we need to better catalog where the pronouns are appearing, on both the redesigned homepage and other public internal pages, as well as private/profile pages?
On the question of what to make the default behavior, we could consider making this clear during registration, noting under the pronoun field whether these are going to appear next to your name publicly or not, and that this can be changed in profile settings later.
Files
- Related to Feature #13347: Add Preferred Gender Pronouns to CAC Profile added
Hi All,
This could get really complex if we want to change WHO the pronouns are displayed to (i.e. logged in vs. out users). For the sake of simplicity, I guess pronouns will be displayed to anyone who can view the commons, so it's a question of where they display.
My initial thought is add several options below the profile area where a user inputs the pronoun information. The options could be something like:
Display Pronouns:
[] Site-wide (anywhere my username appears)
[] Profile only
[] Profile + created content (i.e. site pages, posts, comments; forum topics, replies)
[] Created content only (i.e. site pages, posts, comments; forum topics, replies)
As a foil to Laurie's well-reasoned suggestion :) here's a way of conceiving the settings in a way that's tied to "who" rather than "what":
Display pronouns to:
[ ] Everyone
[ ] Logged-in members of the Commons only
[ ] My friends and members of my groups and sites
[ ] My friends
The third option in particular seems important, because it's in the context of groups and sites where people are likely to be in conversation with each other, thus necessitating the use of pronouns.
Thanks for laying out this other option Boone.
From our chat on the dev call earlier this week it sounds like controlling for WHO can see pronouns would be better route to go.
So, perhaps we can add a drop down option in the profile>edit area that allows a user to select:
Display pronouns to:
[ ] Everyone
[ ] Logged-in members of the Commons only
[ ] My friends and members of my groups and sites
[ ] My friends
- Target version set to 1.19.0
Could we try to make a final decision about this during this week's meetings? There's a possibility of doing it for 1.19 but we need to be agreed on the approach.
Just wanted to note that we do have a page where users can change the visibility setting for each profile field under "My Settings > Profile Visibility".
The "Pronouns" field is already on this page with the following options:
- Everyone
- Only Me
- All Members
- My Friends
The one option that is missing is "My friends and members of my groups and sites". I believe we might be able to plug in this option into BuddyPress, but we'd need to take a further look.
Then we'd need to reference this visibility option before outputting the user's pronouns.
Thanks, Ray! I was planning to integrate into this. (It's currently ignored in many contexts, given the way that the display names are filtered.)
- Status changed from New to Testing Required
Hi All,
For some reason I can't see the option to change pronoun visibility on cdev? Screenshots attached.
If I could see the pronoun options, I think I should have the option to "change" in the edit profile area, and should see a drop down in the profile visibility area?
Sorry, Laurie! I needed to make a database-level change on cdev for you to see the options. Please try again.
Yep, this worked as intended for me. Looks good!
- Status changed from Testing Required to Resolved
Also available in: Atom
PDF