x/website has an excellent test for issue #37047 that catches various problems in Markdown/HTML content. However, there's some content like the upcoming release notes draft written outside of the x/website repository, so sometimes we'll learn about a problem only after the CL was already submitted. That usually means a follow-up CL ends up being needed, like CL 600656 (for issue #68575), CL 587415, etc.
We can configure LUCI to automatically add an x/website trybot and run this test whenever files in doc/next of the main Go repo are modified. That should help catch these kinds of issues.
CC @golang/release, @jba.
Comment From: gopherbot
Change https://go.dev/cl/601656 mentions this issue: main.star: add a linux/amd64 x/website trybot for release note CLs
Comment From: gopherbot
Closed by merging CL 601656 (commit golang/build@0ec9bc3e4337154adcef2357ae4c959ffb02eac1) to luci-config.