Comment on FEP Tracker Tool
Currently we mostly parse the categories from titles, based on certain keywords. It’s not an exact science. The one exception is “informational”, which comes from the index.json FEP listing. If there were more categories listed in there, I could update it more precisely, but for now I am going based on name keywords.
We can define a new metadata attribute for categorization: #520 - [META] Tags - fediverse/fep - Codeberg.org
There are several things that need to be decided before we move forward with this:
tags,categoriesor something else?tags is better than categories, imo. The tracker originally used categories from the existing frontmatter field, and it led to inconsistencies. I’ve just updated the tracker with a cleaner categorization schema based on keywords only, but can adapt it to whatever system we come up with.
Hybrid. A recommended vocabulary of tags that authors are encouraged to draw from, plus the ability to add new tags when none fit.
If we’re defining a new categories/tags field in #520, we should standardize it on YAML inline lists from the start, and potentially use this as the opportunity to also resolve #177 and #824 by migrating authors and relatedFeps to the same format.