If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

profiles: improve expertise block

RESOLVED FIXED

Status

Mozilla Developer Network
Profiles
P3
normal
RESOLVED FIXED
6 years ago
a year ago

People

(Reporter: retornam, Unassigned)

Tracking

(Blocks: 1 bug)

Details

(URL)

(Reporter)

Description

6 years ago
An area of expertise section should be implemented under a users profile page

https://developer-stage9.mozilla.org/en-US/profiles/
Whiteboard: u=contributor c=profiles p=
Target Milestone: --- → 2.0
Don't we already have this...?
Or, is this talking about something different than what shows up here?

https://developer.mozilla.org/en-US/profiles/lmorchard/
(Reporter)

Comment 3

6 years ago
(In reply to Les Orchard [:lorchard] from comment #2)
> Or, is this talking about something different than what shows up here?
> 
> https://developer.mozilla.org/en-US/profiles/lmorchard/

 We do, Luke wanted a bug for it and asked me to file one
Hmm ... on my latest mdn box, I couldn't find a way to *add* expertise thru the edit profile page. Was I missing something? So this might just be a bug where the box for adding expertise doesn't show up sometimes.
Only show expertise block if the profile contains one of the "curated" interests from https://github.com/mozilla/kuma/blob/master/apps/devmo/__init__.py#L46
Summary: Implement areas of expertise under profile pages → profiles: only show expertise block if interests match list
Craig, what do you think for the UX? Users can only add an interest as an expertise if it matches the curated interests list. Should we hide the block if their interests don't match the list, or should we add messaging to the effect?
Summary: profiles: only show expertise block if interests match list → profiles: improve expertise block
Probably worth followup bugs, but we eventually intended all these tags for interests and expertise to turn into tag search links to find users.
Summary: profiles: improve expertise block → profiles: hide expertise block if not applicable
Whiteboard: u=contributor c=profiles p= → u=contributor c=profiles p=1
Assignee: nobody → lcrouch
Enforcing my own rule: saying "no" to most non-migration tasks.
Summary: profiles: hide expertise block if not applicable → profiles: improve expertise block
Whiteboard: u=contributor c=profiles p=1 → u=contributor c=profiles p=
Target Milestone: 2.0 → ---
Assignee: lcrouch → nobody

Updated

5 years ago
Priority: -- → P3
(Assignee)

Updated

5 years ago
Version: Kuma → unspecified
(Assignee)

Updated

5 years ago
Component: Website → Landing pages
Product: Mozilla Developer Network → Mozilla Developer Network
Component: Landing pages → User profiles
Whiteboard: u=contributor c=profiles p=

Updated

3 years ago
Blocks: 962556
Commit pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/634b171f76c44b831197c3dca32c979b64325c12
Fix bugs 1271503, 1274688, 1036150, 712337: Fix profile format and errors.

Fix bug 1271503: Reformat profile.
Moved user links into main profile section. Removed styling for user-photo because it assumed user-links were after it. Reformatted user links to be inline. Some RTL fixes

Fix bug 1274688: JS error on profile.
Included jQuery UI to stop JS errors

Fix bug 1036150: Can't add expertise.
Changed from .attr(checked) to .prop(checked).

Fix bug 712337: Improve expertise.
Show expertise field only if there is expertise for the user to check.

Updated

a year ago
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.