What
Let users add and edit personal fields on their own profile. All fields public.
MVP fields:
- Bio / about me (short free text)
- Degree / course (e.g. Bachelor of Computer Science)
- Year level or expected graduation year
- Social / contact links (GitHub, LinkedIn, Discord, personal site)
Why
- A profile today is only an avatar and a username. The panel shows a "More personalisation stuff coming here soon!" placeholder, and there is commented-out bio and degree markup that was never wired up: profile-panel.component.html
- A few fields give each reviewer an identity and a reason to visit their profile.
Keep the authcate visible
- Username defaults to the email prefix and can be changed. The authcate is that prefix from a Monash student email (e.g. jfer0043 from jfer0043@student.monash.edu).
- Show the authcate on the profile even after a user renames their username.
- Reason: an always-visible authcate ties reviews to a real person and discourages bad posts. The changed username alone hides who wrote what.
Scope
- Add the fields to the user schema, the API, and an edit form on the own-profile view.
- All fields public to everyone at /user/:username.
Touch points:
Out of scope
- Banner / cover images
- Accent colours or profile themes
- Per-field public/private toggles
What
Let users add and edit personal fields on their own profile. All fields public.
MVP fields:
Why
Keep the authcate visible
Scope
Touch points:
Out of scope