[Enhancement] - Update naming for Civic Profile and/or Profile

[leekahung]

Describe the Current Behavior/Feature:

At the moment there is quite a bit of confusion about the differences in Profile and Civic Profile due to the wording, but I think I have a solution to this. We could have "Profile" be changed to "Account" and "Civic Profile" be changed to "Profile" proper.

[Update 12/09/2023] - Other naming conventions could be used as well to make the two distinct. Several other ideas has been proposed such as:

1. convention for things associated with webIds like "user menu/user settings"
2. utilize alternative wording such as "account"/"settings"
3. utilize prefix words like "Pod" or "PASS" to associate profiles like what's done with "Civic Profile"

Rationale:

To clear up what we have now with regards to user information and account information.

Proposed Implementation (if applicable):

For this implementation we could simply rename the pages and routes accordingly.

[xscottxbrownx]

@leekahung - how far do you want to go with this one?

I started, and it just kept going and going.

Do we just want to change anything user facing to Account/Profile, or do we want to change everything?

Doesn't matter to me either way, but if we want to change all functions and objects and such, then I'll go about this a smarter way and commit a component, a util function, etc at a time.

[leekahung]

Do we just want to change anything user facing to Account/Profile, or do we want to change everything?

Doesn't matter to me either way, but if we want to change all functions and objects and such, then I'll go about this a smarter way and commit a component, a util function, etc at a time.

Think we could see how far it'll go first. If the PR gets too big, we can split it up then.

[timbot1789]

I think part of the issue here is that the data in the public profile comes from the WebId, which is used by virtually every Solid app. Giving a distinct name to it may be confusing to some people using several different solid apps. The Element program, which is a client for a decentralized chat protocol called matrix, has a similar identity issue. They use terms like "user menu" and "user settings" for info analogous to the WebId. Maybe we could do something like that?

I think just calling the civic profile "profile" is a bit too vague. It doesn't communicate the information that's contained in the document.

[andycwilliams]

Agree with Tim. I hesitate deviating too much from what's already commonplace. Maybe simply change Profile to Contact Profile (while also changing Profile to Account)? That would make a clearer connection to the Contacts section. I have no definitive stance on this at the moment.

I'd like to get some feedback from caseworkers with this and see if any versions are more intuitive than others.

[leekahung]

Pretty open to making the two entities distinct with naming. Think we just need a consensus on those name.

[leekahung]

For what we have now as "Profile", I'm thinking we could perhaps prefix it with Pod, so something like "Pod Profile/Account/Settings/Menu". It'll help users associate the information there with their Pod specifically.

For "Civic Profile", think we could still use the name "Civic Profile". Though the Element example with "User" sounds pretty good too, so something like "User Profile". We could also use something like "PASS Profile", which associates it with PASS specifically.

[xscottxbrownx]

Well, then I will stop at the 4hrs put into this already until this convo is hashed out.

[timbot1789]

For what we have now as "Profile", I'm thinking we could perhaps prefix it with Pod, so something like "Pod Profile/Account/Settings/Menu". It'll help users associate the information there with their Pod specifically.

For "Civic Profile", think we could still use the name "Civic Profile". Though the Element example with "User" sounds pretty good too, so something like "User Profile". We could also use something like "PASS Profile", which associates it with PASS specifically.

The Element example is in reference to what you called "Profile" or the web ID. "Pod profile" is inaccurate because the web ID is on a higher level than the pod.

"PASS profile" and "User Profile" are a bit imprecise as well. The data isn't PASS specific, it's intended to be shared with other groups. User Profile doesn't convey that the data is confidential and important for legal purposes. It can also be easily confused with the WebID.

The questions here are:

• What is a good name for the WebID that conveys its purpose to the user in a clear and friendly way?
• What is a good name for the object we store HMIS data in that conveys its purpose to the user in a clear and friendly way?

I don't have a strong opinion on the answer to question 1. Maybe something like "user settings" or "ID settings." I think "civic profile" is a good answer to question 2.

[timbot1789]

We also don't need to allow editing of the web ID. It's not a core feature of the app.