-
-
Notifications
You must be signed in to change notification settings - Fork 777
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
Add Filter Tags to Homepage project filters #1201
Comments
Call the new class filter-item |
ProgressAlmost complete. Struggling with css BlockersAwaiting Closure on
AvailabilityHere and There ETAApproximately a week from whenever the above PR's are closed |
@daniellex0 the "(1)" "(2)" and "(5)" placement in the figma design, is the decision to "add" numbers together, under certain cases? i.e., my question comes up when imagining a scenario where an individual comes to the page, goes to the "Looking" dropdown menu, and decides to checkbox both "Development (12)" and "Content (4)". "Looking" would then become: "Looking (16)" I'm assuming "Looking (12), (4), etc.." isn't desired |
@erikaBell Its the number of items selected.
Looking would then become : "Looking (2)" |
@akibrhast Ah, thanks! |
Progress Update: just need to work out a bug with one of the dropdown menus. |
Overview
We need to add filter tags below the homepage project filters so that users can immediately know which filters they selected, and can remove any filters easily.
This also involves adjusting some of the current filter functionality (selected filter categories no longer turn pink- instead they display the number of filters selected in parentheses)
Action Items
Resources/Instructions
Homepage
Figma design for homepage filter tags (in purple rectangle)
Example of filter tags in Best Buy website
Wins page
New filter tag designs (click arrow)
One filter selected:
Multiple filters selected:
So that you know what to look for- this is what the filter tags section in the purple rectangle looks like in the Figma homepage file:
The text was updated successfully, but these errors were encountered: