SolidOS / SolidOS/profile-pane
Data: Heading Job Title and Organization name
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 11
- Avg merge
- 4h 19m
- Merged PRs (30d)
- 11
Description
In the new design there is
- Role/Job Title displayed
- Role/Job Title and Organization Name for editing
There are no special predicates for these to indicate this is the data for the Heading only. Only predicates in the resume data itself, for example of resume data see below.
Notes for discussion
- Does it make sense to have a special Role predicate for the Heading, as this field is displayed as well as in the Edit Dialog?
- Does it make sense to have a special predicate for the Organization Name on the Heading? This field is only for editing it doesn't reflect on the users profile. Also, would this follow resume data... tied to the Organization type etc... or just a standalone Organization name.
- If we add Organization Name should we display it on the profile heading?
Resume Example
vcard:role "Software Engineer";
org:organization :id1779615186286 .
:id1779615186286
a schema:Corporation, vcard:Organization;
schema:name "Microsoft";
schema:uri "www.microsoft.com";
org:location "San Diego";
solid:publicId ent:Q2283 .
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by reviewing the profile heading and edit-dialog data flow alongside the resume example; resolve whether heading-specific role and organization predicates are needed, how organization data should be modeled, and whether the organization is displayed. Done means the predicate and display/edit behavior are agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100