ER: some projects are not filtered correctly by Languages/Technologies

[nnr-nnr]

Emergent Requirement - Problem

Some projects are not displayed when the Languages/Technologies filter is used on the Projects page (and potentially other pages where this projects filtering feature is used).

Issue you discovered this emergent requirement in

• Fix Program Areas filter for Diversity, Equity & Inclusion #4120

Date discovered

3/26/23

Did you have to do something temporarily

• NO - does not affect the issue

Who was involved

@t-will-gillis , @nnr-nnr

What happens if this is not addressed

Some projects will not show up when they should when the Languages/Technologies filter is used. For example, if someone is searching for projects in the Program Area "Diversity / Equity / Inclusion" and that use CSS, the Write for All project will not be displayed even though it meets these two criteria.

Resources

N/A

Recommended Action Items

• Make a new issue
• Figure out which projects this bug affects (so far, it appears to affect at least the Write for All and Heart projects)
• Discuss with team
• Let a Team Lead know

Potential solutions [draft]

Some possible places where this bug may be occuring:

• The collection of projects: see .md files in the _projects folder without the technologies attribute do not allow filtering by Languages/Technology.
• From Will:

In the /current-projects.js file line 27 the filter code is else if (filterName == 'technologies' ) use the filterTitle = 'languages / technologies' so if the card doesn't have the technologies attribute it is ignored. This might be an easy fix but it could also turn out to be a lot of refactoring.

[github-actions]

Hi @nnr-nnr.

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

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

[t-will-gillis]

• Link to the new issue: Fix of Languages/Technologies Filters on Projects and Homepage #4587