Skip to content

ER: Toolkit and Project Filter Maintainability and User Experience Improvements #5233

@Adastros

Description

@Adastros

Emergent Requirement - Problem

While reviewing the pull request linked below, I discovered the following:

  1. The toolkit and projects filters were coded differently even though they perform the same function. This is due to how the toolkit and projects pages are coded. The pages and filter code should be refactored so that the filter can be a reusable component and the pages only import one version of the filter code
  2. The scrollbar appears but doesn't scroll when a filter section overflows
  3. Some filter tags contain overflowing text
  4. The mobile-view of the filters do not scroll properly and some content is cut-off at the bottom of the filter
  5. The filter arrows are not user friendly

See this comment and this comment for more details

Issue you discovered this emergent requirement in

Date discovered

  • 08JUN2023

Did you have to do something temporarily

  • YES
  • NO

Who was involved

@kwangric
@chrismenke45
@Adastros

What happens if this is not addressed

  • Maintaining and updating the project and toolkit filters will be difficult
  • User experience will be hampered

Resources

Recommended Action Items

  • Make a new issue
  • Discuss with team
  • Let a Team Lead know

Potential solutions [draft]

  • Option 1:
    • Create an issue to refactor the project and toolkit filters. Wait for the refactor to complete before creating issues to fix the UX portions of filter.
  • Option 2:
    • Create one issue to refactor the project and toolkit filters and fix UX elements at the same time
  • Option 3:
    • Create issues to fix filter UX. Once the issues are completed, create an issue to refactor the project and toolkit filters.

Metadata

Metadata

Assignees

Labels

Complexity: Extra LargeComplexity: MediumComplexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelComplexity: SmallTake this type of issues after the successful merge of your second good first issueDraftIssue is still in the process of being createdEREmergent RequestIssue Making: Level 2Make issue(s) from an ER or EpicP-Feature: Home pagehttps://www.hackforla.org/P-Feature: Projects pagehttps://www.hackforla.org/projects/P-Feature: Toolkithttps://www.hackforla.org/toolkit/ready for dev leadIssues that tech leads or merge team members need to follow up onrole: front endTasks for front end developerssize: 0.5ptCan be done in 3 hours or less

Type

No type

Projects

Status

QA

Relationships

None yet

Development

No branches or pull requests

Issue actions