Keep manual CSV import into a Google Sheets template as an option for `next` version

[gerardo-rodriguez]

TODO

• [ ] Create a next Google Sheets template
  • connect with @grigs as he may have the most up-to-date Google Sheets to use as the next starter template
• [ ] Add back instructions for how to manually import CSV into Google Sheet template

[calebeby]

A challenge with using this approach is that lighthouse-parade@next modifies the spreadsheet based on the data coming out of lighthouse. For example, the number of graphs, the cell coloring (green=low number vs green=high number), and the information below the mean/median on the page with the charts (Lowest scores or Highest values), and skipping making charts for some audits are all are based on the actual data that comes out of the lighthouse reports. The new --lh:only-categories flag controls which categories of audits lighthouse will run, so the columns of the output (and all of those formatting changes that I mentioned) will need to be different based on that flag. If we had a single google sheets template, it would have to be generic enough (by removing those specific formatting choices) to work regardless of the columns that are in the CSV.

Another option might be to save lighthouse reports as JSON to a folder, and allow passing a flag for lighthouse-parade to "slurp up" these JSONs and put them in a spreadsheet, with all the nice formatting stuff that can only happen if we know the actual column types of data that lighthouse is giving us

[gerardo-rodriguez]

Thanks, @calebeby. I like your JSON idea. That might be the better alternative.