Oleksandr ShyshatskyiandClaude Opus 5 0af15a549a The front page shipped with broken images and literal [x] boxes. ...

Three defects, all in the site machinery rather than the prose, all visible
on the first page anyone opens.

`r"\1=\""` is not an escaped quote. In a raw string that backslash is a
character, so every `src="docs/…"` the README hook rewrote came out as
`src=\"helixscreen-print-status.webp"` and the browser asked for a file whose
name began with a quote. Both screenshots on the front page 404'd.

`- [x]` is python-markdown's plain list syntax unless pymdownx.tasklist is
enabled, so the Status checkboxes -- the list this project leads with, and
the thing a reader decides on -- rendered as the literal text `[x]`. Enabled,
with custom_checkbox so they get the theme's own mark. The checklists in
is-this-for-you.md and after-the-flash.md were the same bug.

And mkdocs rewrites markdown links but not raw HTML attributes, which is
invisible until a page with an `<img>` in it is not the front page: with
directory URLs, is-this-for-you.md is served from /is-this-for-you/, one level
below the image it names. The hook now rewrites relative src/href in raw HTML
too, prefixing `../` per level of the page's own URL, so an `<img>` works from
wherever the page ends up -- and it points at a file that must exist, so a
typo stays a broken link the build can still catch.

Found by serving the site and looking at it, which is the only way any of
these three surface: --strict validates markdown links, and every one of
these was in HTML or in text it had no reason to read.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S3XZh4SqPdXAowVndz6tMr

2026-08-28 22:24:39 +03:00

..

mkdocs_readme.py

The front page shipped with broken images and literal [x] boxes.

2026-08-28 22:24:39 +03:00