Unlike previous PRs, since we are separating the tables and attaching them to different places (divs), we must manually (still programmatically) locate the data-portions in the tableJsonOsf.json.
As a result, the automation process is greatly limited from the point of view of uploading new data.
Important
the relative path tableJsonOsfUrl in Database.md file may not work. In that case, we have to replace it with the absolute github url of the ./automation/output/tableJsonOsf.json
Unlike previous PRs, since we are separating the tables and attaching them to different places (divs), we must manually (still programmatically) locate the data-portions in the
tableJsonOsf.json
.As a result, the automation process is greatly limited from the point of view of uploading new data.
Important
the relative path
tableJsonOsfUrl
inDatabase.md
file may not work. In that case, we have to replace it with the absolute github url of the./automation/output/tableJsonOsf.json