To make it easier for reporters and editors to find, reference and download the data files we are archiving, let's create a simple web page that lists each of the .csv files we've archived, along with a download link.
It might also be helpful to list each version of each csv file so that folks can rewind to previous versions of the data.
A couple of routes we discussed:
Serving static content via the same AWS S3 bucket where we are writing the data files; or
Serving via GitHub pages, which would entail writing the .html file to this project's remote repo.
Either approach would prob work as part of a continuous deployment process so that we can update the page whenever we push code to the main branch.
To make it easier for reporters and editors to find, reference and download the data files we are archiving, let's create a simple web page that lists each of the .csv files we've archived, along with a download link.
It might also be helpful to list each version of each csv file so that folks can rewind to previous versions of the data.
A couple of routes we discussed:
Either approach would prob work as part of a continuous deployment process so that we can update the page whenever we push code to the main branch.