Fix of Languages/Technologies Filters on Projects and Homepage

[t-will-gillis]

Overview

We need to fix a bug affecting the project filters on the Projects and Home pages so that website visitors are provided accurate results from their selections.

Details

On the Projects and Homepage, the Project list can be filtered via various selections. It can be seen that some projects will not show up when they should when the "Languages/Technologies" filter is used. For example, if someone is searching for projects that match a.) the Program Area "Diversity / Equity / Inclusion" and that also b.) use CSS, the Write for All project will not be displayed even though it meets these two criteria. See the following screenshot for an example.

Example Screenshot

Action Items

• Determine which projects this bug affects (so far, it appears to affect at least the Write for All and BallotNav projects and likely more)
• Confirm that the bug coincides with projects that do not have "Technologies" listed
• Note: In the /current-projects.js file, the filter code includes on lines 27-28 else if (filterName == 'technologies' ) then use the filterTitle = 'languages / technologies'. From these lines, it appears that if a project card doesn't have the technologies attribute, then it is ignored.
• Change code as needed, then confirm with Docker that filter is working correctly.

Resources/Instructions

• ER associated with issue: ER: some projects are not filtered correctly by Languages/Technologies #4389
• Projects and Homepage
• /current-projects.js
• /projects folder

[github-actions]

Hi @t-will-gillis.

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

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 Prioritization" label once it is ready for prioritization.

Additional Resources:

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