You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there is a messy table in the README for the schema repo that categorizes tools by purpose and language.
There is also an attempt to build a catalogue in a separate .md file in the schema repo.
The following are two ideas how to improve on these efforts.
A dedicated tools page on the CFF website that provides functionality to "search"/filter for tools. This could work as follows.
We collect the tool metadata in a structured format. For the future, this could be done via an issue template that provides a form for people to enter the info about their tool. A new issue with this template triggers a CI job that writes the information into the structured format, and puts up a PR with the new structured tool info against a repository (perhaps a separate repo, perhaps the website repo, depending on what's next)
We have a web app fo some sort that reads the structure info for all tools, and generates different views on the data. Users can filter for, e.g., purpose and language and get presented with a list of the tools that match their criteria.
The web app is presented as part of the website (technically, either implemented in the website repo via JS or similar, or a separate app hosted on a dedicated website route (e.g., the way gh.io does this with project pages)).
We get our own org on the RSD which users can filter for, and push info for all the tools there, so that people can have more info on the tools, which get their own "homepage".
The text was updated successfully, but these errors were encountered:
Currently, there is a messy table in the README for the schema repo that categorizes tools by purpose and language.
There is also an attempt to build a catalogue in a separate .md file in the schema repo.
The following are two ideas how to improve on these efforts.
The text was updated successfully, but these errors were encountered: