ci: replace htmlproofer with wjdp/htmltest

[dvdksn]

Signed-off-by: David Karlsson david.karlsson@docker.com

Proposed changes

This replaces the Ruby-based htmlproofer with htmltest

This tool runs faster and seems to provide additional checking capabilities and more configuration opts.
(Most of which I have disabled for now, since we're violating them 🙈)

Related issues (optional)

[netlify]

✅ Deploy Preview for docsdocker ready!

Name	Link
🔨 Latest commit	13696ba
🔍 Latest deploy log	https://app.netlify.com/sites/docsdocker/deploys/6436b4b6b635d700082b3f32
😎 Deploy Preview	https://deploy-preview-17096--docsdocker.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[thaJeztah]

I'm curious now what we used before htmlproofer (we had a linter before that, but I forgot what it was)

[thaJeztah]

Oh! never mind, looks like it was htmlproofer as well, but as a separate check; #13514

[dvdksn]

the test works, it's failing because of some file in an upstream compose repo has a bad link

[crazy-max]

the test works, it's failing because of some file in an upstream compose repo has a bad link

@docker/compose-maintainers https://github.com/docker/docs/actions/runs/4678750123/jobs/8287857444?pr=17096#step:5:60

[dvdksn]

I will add compose/compose-file to the ignore list for now.

[thaJeztah]

Oh! Those are the fun ones. Does it allow for "warning" <--> "error" for certain files (that are maintained elsewhere?) Or at least until we have a proper baseline?

(worst case, we could push some temporary commits to manually patch things if they are "vendored" in this repository)

[dvdksn]

we could push some temporary commits to manually patch things if they are "vendored" in this repository

Unfortunately they are not vendored, but pulled during build :( so I think the pragmatic way fwd is to ignore these files until they are fixed. Buildx uses a docs validation workflow that performs the linting on changes in the upstream.

[crazy-max]

we could push some temporary commits to manually patch things if they are "vendored" in this repository

Unfortunately they are not vendored, but pulled during build :( so I think the pragmatic way fwd is to ignore these files until they are fixed. Buildx uses a docs validation workflow that performs the linting on changes in the upstream.

Yeah maybe compose should have this kind of validation too

[milas]

Is this the workflow we should copy for Compose spec? https://github.com/docker/buildx/blob/master/.github/workflows/docs-upstream.yml

[crazy-max]

@milas Yes