Skip to content
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

CTA / Organization / Create #2014

Open
paulsonder opened this issue Nov 25, 2024 · 6 comments
Open

CTA / Organization / Create #2014

paulsonder opened this issue Nov 25, 2024 · 6 comments
Assignees
Labels

Comments

@paulsonder
Copy link
Member

paulsonder commented Nov 25, 2024

As a user, I want to be able to Create and Organization so that I can organize content separately from my own personal namespace and collaborate with other users.

Acceptance criteria

  1. User clicks to create a new Organization
  2. User completes Create Organization form

Design docs

Entry points

Users are able to create an Organization by clicking on the 'Create' menu in the main Navigation bar or from the Quick Links drawer...

Screenshot 2024-11-25 at 15 47 44 Screenshot 2024-11-25 at 15 42 04

Forms

The Create Organization forms can be found here.

@paulsonder paulsonder self-assigned this Nov 25, 2024
@paulsonder paulsonder added the V3 label Nov 25, 2024
@paulsonder paulsonder added this to v3 Nov 25, 2024
@paulsonder
Copy link
Member Author

@jamlung-ri A few questions for you...

  1. Should we allow a user to create and manage custom attributes for an Organization? Are there use cases for this? If Yes, is it something we can push to post-launch as a topic?
  2. Should we make uploading an avatar mandatory? If not an image, should there be a fall back with an initial or other idea to make the avatar a little more distinctive with a view to making them more visible in search results etc?

@jamlung-ri
Copy link
Member

jamlung-ri commented Nov 25, 2024

1. Should we allow a user to create and manage custom attributes for an Organization? Are there use cases for this? If Yes, is it something we can push to post-launch as a topic?

It's definitely uncommon, but it feels like something that could be built in without a lot of emphasis. OCLv2 allows you to create them, but they aren't heavily encouraged in the Create Org form.

But extra attributes are something that people might want to have displayed on the org's Overview tab too as a way to provide more structured info about themselves, in a visual that isn't far off from the way that a Repo would display FHIR attributes.

2. Should we make uploading an avatar mandatory? If not an image, should there be a fall back with an initial or other idea to make the avatar a little more distinctive with a view to making them more visible in search results etc?

Is that common in other tools? I agree that giving users something distinctive would be good, but I don't know what the common approach is. It especially feels like it could deter users from creating a user profile if they feel like they have to input an avatar of some sort.

I could get on board with a "Hey I know you hit submit but you didn't put a profile pic! These help people know who you are, and it doesn't even have to be your picture..." approach, but allow people to bypass it if they really don't want to put something.

Also, GitHub's might be a good example where people are given a semi-unique picture if they don't assign one themselves.

@paulsonder
Copy link
Member Author

  1. So maybe Custom org attributes could be displayed in the same format as FHIR attributes are in the Repo overview, using the structured list component?
  2. Applications usually provide some kind of fallback, others will create an avatar from your initials (I can't imagine this option being useful for an Org as opposed to a person with first an last name). I think a logo should be encouraged, but not mandatory, with a better fallback than we're using currently.

@jamlung-ri
Copy link
Member

jamlung-ri commented Nov 25, 2024

  1. So maybe Custom org attributes could be displayed in the same format as FHIR attributes are in the Repo overview, using the structured list component?

Yeah I think that could be ideal!

2. Applications usually provide some kind of fallback, others will create an avatar from your initials (I can't imagine this option being useful for an Org as opposed to a person with first an last name). I think a logo should be encouraged, but not mandatory, with a better fallback than we're using currently.

Agreed, encouraged but not mandatory is the ideal approach, and perhaps with an Identicon or Jazzicon fallback?
https://identicon.net/
https://www.npmjs.com/package/jazzicon

@paulsonder
Copy link
Member Author

That's interesting! To be clear here though, these are Org images, not User

@jamlung-ri
Copy link
Member

Good point, I don't know if it's a good idea to have slightly different approaches between Users and Orgs, but we could stand to push a little harder to populate an avatar when creating Orgs. Even so, some sort of visual identity fallbacks for both types would be good to have nailed down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

2 participants