Create a Product Security Wayfinder component

[northdpole]

Issue

We created the first Wayfinder manually here https://owasp.org/projects/
It's cool, the community has embraced it but it's manual and currently sits in a shared drive.

Expected Behaviour

As an OpenCRE.org user I can browse a graphical way of exploring tools and standards known to OpenCRE by grouping them on which part of the SDLC they map to. Similar to the wayfinder above.

I can filter the new wayfinder by selecting supporting organizations, licenses or any other Key from the metadata fields.

Actual Behaviour

We have the data to automate the creation of the wayfinder, let's do so.

To achieve this we need to

• grab unique names from every non-cre node in our database
• enrich them with metadata such as SDLC steps they fit into
• find a way to automatically provide this info on import (e.g. by modifying our importers or creating a static map to start and then require projects to add this info in their self contained links)
• present this info in a frontend in a nice way allowing for filtering based on supporting org, license, and other metadata we may have

[HimasreeKolathur24]

Hi! This looks like a really interesting feature.

Is there any design discussion or preferred frontend stack for implementing this component? I’d love to understand the expected architecture before exploring further.