mkdocs is kind of in turmoil. an incompatible 2.0 release came out. it
was covered by the mkdocs-material folks in:

https://squidfunk.github.io/mkdocs-material/blog/2026/02/18/mkdocs-2.0/

and led to them rewriting mkdocs from the ground up into a separate
project called zensical, which has a RFP in #1145065. it's not fully
backwards compatible with mkdocs (yet) nor will it be byte-for-byte
identical anyways.

Another view of the collapse was documented here in March 2026:

https://fpgmaas.com/blog/collapse-of-mkdocs/

So other folks have forked mkdocs. The most promising seems to be
properdocs:

https://properdocs.org/

There's a little bit of drama in the background of how it was created,
visible here:

https://github.com/orgs/ProperDocs/discussions/1

In there, you can see that properdocs folks actually took over the
mkdocs pypi namespace for a while, and the zensical maintainer has
called out properdocs maintainers for "acting in bad faith" in:

https://github.com/squidfunk/mkdocs-material/issues/8581#issuecomment-4198060422

zensical maintains a timeline of this fiasco in:

https://squidfunk.github.io/mkdocs-material/blog/2026/02/18/mkdocs-2.0/#august-2026

Still, it looks like paperdocs is the best maintained (or most
well-known?) mkdocs fork out there and perhaps we should just switch
to it.

Either way, mkdocs is currently unmaintained and I don't think it
should be released in Debian 14.