Beyond detecting well-identified errors or opportunities for improvements, it would be really nifty if the checker provided more open-ended guidance to its users when it detects some patterns in the code.
For instance:
if the code use "large" raster images, it could draw attention to responsive images with the srcset attribute and the picture element
if the code use ApplicationCache, it could draw attention to service workers
if the code use "Web app metadata", it could draw attention to the work on the manifest spec
Ideally, this contextual guidance would be easily added and removed from the checker, possibly from a community-maintained repository of hints. I would imagine it as a JSON file that lets one associate with some code patterns a resulting suggested hint.
Beyond detecting well-identified errors or opportunities for improvements, it would be really nifty if the checker provided more open-ended guidance to its users when it detects some patterns in the code.
For instance:
Ideally, this contextual guidance would be easily added and removed from the checker, possibly from a community-maintained repository of hints. I would imagine it as a JSON file that lets one associate with some code patterns a resulting suggested hint.