Does anyone else see value in having a target overview page like this? A table of targets per backend? https://docs.bazel.build/versions/main/be/overview.html I personally love this

I want a development glossary for sure 😃

Yeah, specifically the "all in one" style - it's also useful for ensuring relative consistency across targets

Maybe after I'm done with all my todos I'll finally sit down and write docs 😂

readme has a Glossary feature that afaik we aren't using. Dunno whether we want to get too attached to their implementation given that the ultimate goal is to finish migrating off readme. But presumably they've put more thought that average into how to use a glossary. So might find some good ideas in their docs.

The glossary could be pretty static once setup, backend targets don't go through too much churn after creation

Oh hmm, their glossary feature is not your glossary feature. https://docs.readme.com/docs/glossary I see value in both.

fwiw, the Target and Subsystem aspects of the site are already generated by

build-support/bin/generate_docs.py

… so adjusting that to generate an additional page based on the “providing backend” information wouldn’t be too bad