A Download Area is added which contains the auto -generated download tables based on the .zip extensions (currently, only country-wise). Thus tedious and error-prone manual-copying in the md files are not needed anymore.
Important to note
The json from which the tables are generated is also programmatically generated by sending only one get request through githubApi (thus, no fear for crossing request limits).
When new data is comitted to the power-grid-frequency-data repo, the maintainer has to execute
only: npm run build in the cloned automation-repo. This will generate the jsons in the output folder. Once the website is stable, we can shift the source of the automation-repo to the central repo, or even leave it where it is to be aligned with github's slogan "distributed is the new centralized"! :smile:
TODO:
Styles of the tables can be updated, but in a different PR.
A
Download Areais added which contains the auto -generated download tables based on the.zipextensions (currently, only country-wise). Thus tedious and error-prone manual-copying in the md files are not needed anymore.Important to note
The
jsonfrom which the tables are generated is also programmatically generated by sending only one get request through githubApi (thus, no fear for crossing request limits).The process is abstracted in this repo: power-grid-frequency-automation
Workflow
When new data is comitted to the
power-grid-frequency-datarepo, the maintainer has to execute only:npm run buildin the cloned automation-repo. This will generate the jsons in theoutputfolder. Once the website is stable, we can shift the source of the automation-repo to the central repo, or even leave it where it is to be aligned with github's slogan "distributed is the new centralized"! :smile:TODO:
Styles of the tables can be updated, but in a different PR.