Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Skills) Search results page revisions #195

Closed
5 tasks
Tracked by #210
jenchuu opened this issue Apr 1, 2022 · 4 comments
Closed
5 tasks
Tracked by #210

(Skills) Search results page revisions #195

jenchuu opened this issue Apr 1, 2022 · 4 comments
Labels
feature: Design System P2: Med-high Medium-high priority PBV: design all issues for design roles role: UI/UX - Design size: 2pt Can be done in 7-12 hours
Milestone

Comments

@jenchuu
Copy link
Member

jenchuu commented Apr 1, 2022

Overview

As a designer, we need to ensure new volunteers understand what skills are required and what skills they'll learn through volunteering on the project cards on the search results page. We will replace or change the tooltip to a tertiary button tooltip ("Are skills required?") or use similar language of CMS pages ("required" or "willing to learn").

Action Items

  • Ideate ways to communicate different types of skills (ex. tertiary button tooltip "Are skills required?" or use similar language of CMS pages "required" or "willing to learn")
  • Log ideations and which are best solution(s) and why in GitHub comments below
  • Present for feedback
  • Decide and implement in Figma
  • Log final design decision here before closing issue

Resources/Instructions

Design prioritization/breakdown

@stephaniestahlberg
Copy link
Member

The CMS research has some findings that are relevant for the language around Skills. Let's discuss after we present.

@sharadgaurav7
Copy link
Member

@stephaniestahlberg , please update this issue with the findings so the UX team will keep records of what was included and why.

@stephaniestahlberg
Copy link
Member

Findings from CMS research on Skills section:

  • Not everyone liked calling this category “Skills”. Some preferred “Technology” or “Tools”.
  • Some teams/roles have required skills/tools, while others would place everything under "Willing to learn."

Recommendations based on these findings:

  • Allow poster to select between "Skills" or "Technologies and Tools"
  • Allow for “required skills” and “willing to learn” to be left empty as needed

@sdimran sdimran modified the milestones: 07.01 - Page Revisions (Desktop), 08 - MVP 2 Page Revisions (Desktop) Apr 22, 2022
@kcoronel kcoronel removed this from the 10 - MVP 2 Page Revisions (Desktop) milestone Feb 14, 2024
@kcoronel kcoronel added this to the 07 - MVP 1 milestone Feb 14, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New Issue Approval in P: CTJ: Project Board Jun 12, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from 🆕 New Issue Approval to 📋 Prioritized Backlog in P: CTJ: Project Board Jun 12, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the PBV: design all issues for design roles label Jun 12, 2024
@nooriaali9
Copy link
Member

Closing this issue - since it is outdated/ not a priority anymore - based off of #552

@github-project-automation github-project-automation bot moved this from 📋 Prioritized Backlog to ✅ Done in P: CTJ: Project Board Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: Design System P2: Med-high Medium-high priority PBV: design all issues for design roles role: UI/UX - Design size: 2pt Can be done in 7-12 hours
Projects
Archived in project
Development

No branches or pull requests

8 participants