Separate Info for Internal and Public User Profile
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Current situation
In the current profile settings, the user can enter one set of personal information and select whether each field is personally, internally or publicly visible. That suits many needs and I like the general approach, but I think that any kind of organization may experience some shortcomings there.
What's missing?
When I work in an organization, I might want to share different information about the same topic depending on whether the viewer is part of that organization or not. To give an example: In the About section, I would want to internally share some personal information about myself (when did I join, what are my interests) with my coworkers. But when I share a link to my profile with someone external (e.g. a client), the About section should rather give some info about my field of work and which topics I am familiar with.
Implementation
I think the most practical way would be to allow the user to add arbitrary many instances for each field (like in the email field) and select the profile visibility for each instance.
With this mechanism, I could easily share my personal and my professional twitter handle with my coworkers while any external person could only see my professional one. I could set my name as "Walter H. White" for external visitors while my coworkers see me as "Walter Hartwell White". I could enter multiple internal organizations like "christmas party comittee", "first responder" and "field engineer" while a client sees "Network Analyst". I think you get the idea.
What do you think about this suggestion? Let's discuss :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the current profile settings and visibility behavior, then clarify the expected internal and external profile views before assessing the scope; done means the proposed per-field multiple values and visibility rules are specified and agreed.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100