The main criteria I believe most begin with is the OS the client will run on. I mean, that filters results substantially, so I’ll want to track it. However, I’m not going to go deeper than “families”, meaning, “Windows, macOS, Fedora, Ubuntu, POSIX”, but not any version numbers. It’s because my list won’t be updated enough to make that info consistently useful; it provides a starting point of projects to check out.
I’ve got a much better idea that me going through all the possible criteria… wikidata!
As in, I’ll import and map data from wikidata! Then I can use the existing data tracked, which is inconsistent between similar records (for instance, for XMPP clients). But since I’m mapping all of them, on my side I’ll point out missing data and will be able to update the wikidata entries, which means also anyone else can also update them! 
That means the next part is actually:
- Generate data feeds of XMPP clients on wikidata
- Import data to custom fields
After a bit of thought I’m taking a longer route, and building the thing I need adjacent to this. It calls for a stats party!
Ahem, what I mean is, I’m building two products:
- a database tool that checks wikidata standardization and is easy to sort
- a curated list of recommended clients, by platform
Both of these serve my goal of assisting the XMPP community, and specifically with new users finding clients they need to achieve their goals (which I believe the majority of XMPP users do).
And it is easier to build the second after the first, so we’ll do that. Which means… hugo and json!