

Somewhat, but I’m thinking of the future of federation as a torrenty mesh of peers with no actual hosting “service” that can be turned off. That’s how I picture the Cortex in the Firefly universe. When Simon as a boy is excited about getting a “source box” I imagine it’s a participant as opposed to just an endpoint.
I think you pretty much just now wrote a landing page, you just need to turn those into links and host that page somewhere.
Sure, you could create a database or JSON file with attributes of each thing and use React or Node.js to generate the UI, but that doesn’t seem necessary for a need on this scale - when things change just edit the landing page. I’ve been keeping links to my soft copies of D&D books and stuff with a simple HTML page for years, and I’m a web dev. No need to do work the requirements don’t demand.