[meta] V2 Report Burndown

[paulirish]

Overview

• Add config v2 MVP [WIP] feat: base config v2 functionality #1880 [@patrickhulce]
• Add --v2 flag. [@brendankenny]

Report sprint

• Add report DOM renderer MVP [@dgozman]
  • Re-sort topics by failures [@robdodson]
  • Hide passing audits [@ebidel]
  • Render Markdown to DOM [@brendankenny]
  • Migrating various formatters to DOM [team]

Audit IA refactor

• Perf metrics move [@patrickhulce]
• PWA topics collapse into audits [@paulirish]

PWA definition - Align PWA items w/ Checklist [@ebidel]

• add TTI < 10s audit [@paulirish]
• Add placeholders for crossbrowser, etc
• Express PWA boolean along with score (decide how score and boolean relate)

[wardpeet]

if it helps I can make the report's styling cross browser ^^

[ebidel]

@paulirish since we can't test the additional PWA checklist items, do we need fake audits for them (crossbrowser, each page has an url, page transitions dont fee janky)? There's already a note at the top of the section that says our items are a subset of the checklist and links to it:

[paulirish]

@ebidel not sure! we could do fake audits (a la comingSoon) or some paragraph text at the end of the section, or something else. The paragraph text doesn't sound so bad to me.

For expressing the PWA boolean I think we should plan on showing like a green checkmark if you're good. So maybe something like

Congrats, you're bonafide!

You've met the requirements for a baseline progressive web app*.

*Baseline PWAs require a few criteria that Lighthouse didn't test. 1) The site must work crossbrowser. 2) Each page must have a URL. 3) Transitions between pages dont feel janky. Read more here.

Just spitballing, so whatever. :)

[paulirish]

closing in favor of the io burndown issue. #1937

i filed the new #2059 to capture our convo here about the untested PWA reqs