Is your feature request related to a problem? Please describe.
There are parts of the website that can use improvements in increasing the accessibility of the website.

**Describe the solution you

Great stuff! I'm planning to use API for my dashboard Pandemic Estimator but I wish your API had a better documentation on methodology. I'm using JHU directly and I know what chaos it is, the most blatant example being that they provide "cumulative data" that's not cumulative quite often in practice. And the whole change of file formats, etc.

Can you please de

As there is constant development on the repository and 5-10 PR everyday. It will be nice if we have test for the components to ensure the code do not break in any manner while getting deployed in prod environment.

Pain point :
Many of our the analysts are not familiar with using the API for analysis.

Solution:
A google script can easily fetch the data from the API and store it in their personal Google Sheet every 30 minutes or so.
If we can create the script and write a simple document on how to do this, it would be a great help!

As the default takes too much space, we can improve this by format it using K per thousands e.g. 300K, 500K etc

server {
    server_name coronastatus.fr www.coronastatus.fr;

    location / {
        proxy_pass http://127.0.0.1:5000;

        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
        proxy_set_header X-Real-IP $remote_addr;
     

The Symptom Report allows the user to proceed past the location step without entering a location. Data without a location is not useful and also causes a server error. The location in this step (but not the tutorial step) should be required.