Tools page refactor (fixes #124) - #131
Conversation
|
If you're not able to set up a local staging instance of the website, https://codemeta.opinions.monster/tools/ is available. The link to the CONTRIBUTING github page in the second paragraph will not work (since this isn't yet merged and deployed). Please use the review workflow for this PR to suggest changes. |
|
@meldra I can merge this if there is no particular preffered PR order to merge. |
|
@moranegg if you can merge #126 i can fix up this PR so it can be available for merging. I would also like us to start a discussion asking for suggestions of missing tools. I'm sure this PR's list won't be complete, and crowdsourcing seems like the best way to remedy that. Do you think that's a good idea? |
LLM assistance (Kimi K2.6 reasoning) was used to scrape the tables and output the initial JSON, which was then manually edited to fill in missing or misplaced information. The LLM also assisted with categorizing the tools into categories based on definitions provided to it. The assigned categories have been reviewed and appear accurate to an unfamiliar eye, but are potentially incorrect and may need adjusting.
|
@moranegg the rebase is done for the current master branch, and this is all good to go when you're ready. |
It does not have a clear meaning since most of the items have mentions in the tool tables.
|
Ok, some final tidying done. Now, for real this time, it is ready! 🤞 |
3 participants
This PR addresses #124 and refactors the tools page from markdown
tables to tables generated from JSON data files with some
configuration regarding the current supported versions in the new
setting
Site.Params.supportedin/config.toml.The content of the tables is still roughly the same, as before with⚠️
the notable change of the main table being split into categories,
and any tools not labelled for supported versions having their own
special table. Tools which are not listed as having support for the
latest CodeMeta version are marked with a warning icon:
The tables are now in html rather than markdown purely for source
readability.
Any tool can be classified into multiple categories. Each tool's
categories should be reviewed by folks with familiarity and any
adjustments made before this PR is merged. These adjustments can be
done via changes to the new JSON files
/data/tools.jsonand/data/tool_categories.json. See the new CONTRIBUTING amendment forspecifics.
LLM assistance (Kimi K2.6 reasoning, via Kagi) was used to scrape
the tables and output the initial JSON, which was then manually
edited to fill in missing or misplaced information.
The LLM also assisted with categorizing the tools into categories
based on definitions provided to it. The assigned categories have
been reviewed and appear accurate to an unfamiliar eye, but are
potentially incorrect and may need adjusting.