Research solutions for broken links and resource integrity

[matthiasrohmer]

developer.chrome.com and web.dev are both statically built. Building DCC alone generates 4300 HTML documents. While we have some tools in place to guarantee the generated pages are well-formed, like Markdown linting and the Chrome DevRel Review bot, it can still happen that changes to logic how the suite is built or served (a filter or one of the redirect handlers) causes links to break. Also external links to GitHub or other Google sites might change over time. To top it of our images are served by Imgix which occasionally fails to serve specific formats (https://github.com/GoogleChrome/developer.chrome.com/issues/4065).

To improve the situation we need a new workflow added to the existing Checks that verifies link and resource integrity in the build output.

After verification we also need to work existing reports on broken links and fix them one after another.

• https://github.com/GoogleChrome/developer.chrome.com/issues/83
• https://github.com/GoogleChrome/developer.chrome.com/issues/4870
• https://github.com/GoogleChrome/developer.chrome.com/issues/2277
• https://github.com/GoogleChrome/developer.chrome.com/issues/1856
• https://github.com/GoogleChrome/developer.chrome.com/issues/1559

[mollietokyo]

Estimate = N/A (linked to issue 46) (SPR-3)