codeforpdx / codeforpdx/PASS

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

Open
#524 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
38
Forks
23
Avg merge
11m
Merged PRs (30d)
4

Description

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the pages and routes for Profile and Civic Profile, then clarify with maintainers which naming convention should be adopted because several alternatives remain open. Done means the agreed names are applied consistently to the affected pages and routes, with navigation and wording no longer confusing the two concepts.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.