Create filter_dropdown.scss File in Elements Folder

[kathrynsilvaconway]

Overview

Currently, the dropdown filters menus on the projects page and the toolkit page use different SCSS classes, which creates visual inconsistency for the user and also makes it hard for future developers to apply changes correctly. We need to create an SCSS file the will contain all the classes necessary to build our filter menus and store it in the elements folder for future use.

Action Items

• create a new SCSS file in the elements folder called _dropdown_filters.SCSS.
• Copy the entire contents of the _project-filter.scss file into the new _dropdown_filters.scss file.
• Import the new scss file you created into main.scss and delete the import for the original _project-filter.scss
• After you verify that the contents has been copied correctly, delete the original _project-filter.scss file in your local repo and test the site to make sure nothing is broken.
• Push your code to your feature branch.
• Demo your code with the merge team/tech leads. Which has not been made at this time. Check the bottom of this issue to see if an issue has been made yet. if not, leave a comment with this issue being done Design a fix the dropdown menu design for projects page #3277, if yes, then release dependency on the new issue that related this one.

Note to Merge Team/Tech Leads:

• If moving this file does not break any code on the site, have the assignee open a pull request and the changes can be merged. If something does break, create an issue to investigate why and correct it.

Resources/Instructions

Here is the _project-filter.scss file:
https://github.com/hackforla/website/blob/gh-pages/_sass/components/_project-filter.scss

[github-actions]

Hi @kathrynsilvaconway.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:
Role, Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[github-actions]

Hi @wendybarrios, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[wendybarrios]

i. Availability: Monday, Tuesday, Thursday : 8:00am - 12:30pm and 6:00 pm - 7:30pm
ii. ETA: Tuesday, 1/17

[wendybarrios]

Blockers: School/Work
Availability: Evenings after 6:00pm
ETA: 1/27