feat: build static datasources

[Eomm]

Relates to #46

TODO:

• generate plugins.json at build time
• generate benchmarks.json at build time - requires Benchmark page #43
• generate team.json at build time
• generate organizations.json at build time
• generate acknowledgements.json at build time

[Eomm]

cc @HassanBahati this PR generates these files that are useful for your index PR #38

• static/generated/organisations.json
• static/generated/team.json
• static/generated/acknowledgements.json

[HassanBahati]

cc @HassanBahati this PR generates these files that are useful for your index PR #38

* static/generated/organisations.json

* static/generated/team.json

* static/generated/acknowledgements.json

this is noted. let me pull the changes

[HassanBahati]

@Eomm am just curious...what could be the upside of having this data in .yml versus .json given that Prevously we had them in json

[HassanBahati]

i've seen a script that generates the .json files....what could be the intent in first having yml then run a script to generate json

[Eomm]

In this way we don't need to update pages/documentation across the organization - it is just another piece of the old website legacy that we could remove after the migration