The Ecosystem consists of projects, tools, utilities, libraries and tutorials from a broad community of developers and researchers. The goal of the Ecosystem is to recognize, support and accelerate development of quantum technologies using Qiskit.
To move the ecosystem page to ibm.com, the devs need the member data. They don't want to have to ping every TOML file because it is too slow. Instead, we should collate every TOML file into a single generated JSON file.
We should still use the TOML files for human editing. This JSON file is only auto-generated to help the ibm.com integration. (We could call it something like members_auto-generated.json or something.)
The schema should be {members: object[]}, i.e. an array of each member with all of its TOML values.
--
To do:
[ ] Add script to auto-generate
[ ] Add validation (CI) that the script is correctly generated. I recommend in CI re-generating the file from scratch and seeing if there is any diff. The open source sync config in closed source docs repo has some examples of how to approach this.
To move the ecosystem page to ibm.com, the devs need the member data. They don't want to have to ping every TOML file because it is too slow. Instead, we should collate every TOML file into a single generated JSON file.
We should still use the TOML files for human editing. This JSON file is only auto-generated to help the ibm.com integration. (We could call it something like
members_auto-generated.jsonor something.)The schema should be
{members: object[]}, i.e. an array of each member with all of its TOML values.--
To do: