Skip to content

Remove "Team" from cc.org profile pages of users who are not on staff, board, or advisory board #1040

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ericsteuer opened this issue Oct 14, 2019 · 2 comments · Fixed by cc-archive/new-www-theme#33
Assignees

Comments

@ericsteuer
Copy link

This may require a discussion outside of GitHub

But I noticed that anyone who has a user profile on cc.org also has a public facing profile page (e.g. https://creativecommons.org/author/alessandro/) with "Creative Commons > About CC > Team >" above their bio and photo (if they have one).

This is confusing, and my feeling is that only current CC staff, board, and advisory council profiles should have the "About CC > Team" categorization

This may actually be a conversation about separating out staff/board/advisory council bio pages from whatever function creates these pages for everyone who has an account, because I also don't see a reason for blog posts to show up under staff profiles at all

@claudiorrrr
Copy link

Related with this, if you go visit this URL, there's nothing there showing that Tim is no longer part of the team. We should come out with a way to address that that is less confusing.

@hugosolar
Copy link
Contributor

hugosolar commented Jan 3, 2020

I was able to identify a non-staff user because its user meta data group does not exist, that way I can assume the user doesn't belong to any group defined in the user edit screen

Screen Shot 2020-01-03 at 12 25 53 PM

So I made these changes:

  • I change the breadcrumb by making a relationship between the non-staff author and the blog
  • Remove the extra information below the avatar when user is a guest

For instance:
Screen Shot 2020-01-03 at 12 13 26 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants