Matthias Rohmer

Reference language versions with link elements

1

This isn't really urgent as there is a workaround, but linking language versions with `` elements is not really easy with Grow because of the "virtually translated documents". What I...

Update and pin karma core and plugins

1

Replaces https://github.com/GoogleChrome/web.dev/pull/7425. This updates and pins karma and its dependencies to their most recent version. Tests work as before, verified by running `ELEVENTY_ENV=prod npm run build && npm run test`.

While waiting for the preview to generate the form should be locked, to signal patience is needed. Also the button should have actual button styles. via @bramus, @samdutton and @tunetheweb.

Instead of having to manually split YAML and document body one should be able to simply paste the full file contents to the handler. 11ty uses https://www.npmjs.com/package/gray-matter internally for this....

Being able to live-edit your document with the preview auto-refreshing would be nice to have for the new preview. via @tomayac.

After you initially logged in for the preview handler for updates you are again asked to select the account you want to use to authenticate. via @tomayac.

From one of the Cloud Build logs ``` Could not minify html for dist/en/blog/new-in-chrome-93/index.html Could not minify html for dist/es/blog/new-in-devtools-96/index.html Could not minify html for dist/en/docs/apps/app_network/index.html ```

Implement `{% ImplementationStatus %}` shortcode to get rid of manual table maintenance

4

Throughout the site we use [manually maintained tables](https://developer.chrome.com/docs/web-platform/launch-handler/#current-status) to communicate the progress a feature has made so far. While the tables are currently labeled as "Current Status" it has been...

Currently the site uses [Percy](https://percy.io/google-chrome/developer.chrome.com) to test PRs for visual changes and potential diffs they introduce. The current config only checks a small subset of hardcoded pages or rather page...

Before actually pushing a build to production we should perform smoke-tests which automatically go over well-known click paths using a headless browser, matching response codes and parts of content with...