Habe gestern diesen Artikel über die Hintergründe bei #Mkdocs gelesen (https://fpgmaas.com/blog/collapse-of-mkdocs/) und jetzt eine Nacht darüber geschlafen. Da wir Mkdocs + Material in der #lernOS Produktionskette verwenden, besteht Handlungsbedarf.

Von den Optionen scheint der Wechsel zu #Zensical naheliegend (https://zensical.org). Feature Parität zu Material ist recht weit, Blogs gibt es noch nicht (auf lernos.org eingesetzt). Werde mal die aktiven Maintainer kontaktieren, damit wir das besprechen.

The Slow Collapse of MkDocs

How personality clashes, an absent founder, and a controversial redesign fractured one of Python's most popular projects.

There's a new piece explaining "The Slow Collapse of #MkDocs": "How personality clashes, an absent founder, and a controversial redesign fractured one of Python's most popular projects."

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

Well, that says a lot. But what's really interesting is that MkDocs 2.x is being developed as part of the "encode" organization. That's great, right? The people who gave us such great libraries as #httpx?

Well, turns out no, not at all. It looks like encode has already crumbled and became immensely toxic.

httpx is not allowing bug reports anymore, apparently because of "absurdly skewed gender representation", whatever that means.

https://web.archive.org/web/20260228113715/https://github.com/encode/httpx/discussions/3784

That also explained why starlette moved out of the organization a while back:

https://web.archive.org/web/20260323042730/https://github.com/Kludex/starlette/issues/3180

There's a great rot in #OpenSource.

#FreeSoftware #Python

The Slow Collapse of MkDocs

How personality clashes, an absent founder, and a controversial redesign fractured one of Python's most popular projects.

Tester et valider mkdocs pour créer un wiki interne de l'entreprise accessible depuis les dossiers partagés (hors forges logicielles) : ✅
#mkdocs #wiki #entreprise #collaborateurs

I just migrated my personal site from Mkdocs to Zensical.

My site: https://maulonobile.codeberg.page/
Learn more: https://zensical.org

#Zensical #MkDocs #Codeberg #OpenSource

MLNotes - MLNotes

maulonobile markdown notes

So, remember how all the cool kids dumped #Sphinx and went for the shiny #MkDocs thing? And then used the shiny Material for MkDocs theme?

Well, apparently MkDocs 1.x is dead, and MkDocs 2.0 is coming with no support for plugins, incompatible theming system, closed contribution model and unclear licensing.

So which hype train are the cool kids jumping to these days?

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

#Python

What MkDocs 2.0 means for your documentation projects - Material for MkDocs

MkDocs 2.0 is a ground-up rewrite of the documentation tool tens of thousands of projects rely on, introducing potentially significant breaking changes

Die Hölle friert zu: Nele Hirsch empfiehlt Publii

Mir gefällt die kompetente und unaufgeregte Art, mit der Nele Hirsch ihr eBildungslabor betreibt, und darin die Themen zur Bildung im digitalen Wandel behandelt. Lediglich eines hatte bei mir immer ein Stirnrunzeln erzeugt: Wenn es um die Frage »Publizieren im Web« ging, kannte sie bisher nur eine Lösung – ein selbstgehostetes WordPress. https://kantel.github.io/posts/2026030402_publii/ #StatischeSeiten #Publii #Webworking #Markdown #MkDocs

So sad to see the Mkdocs drama leading to a version 2 which smells lock-in by a lonely developer ignoring a community of thousands of users/contributors and the other part the @zensical team releasing a latest version of unmaintained Material for Mkdocs with a huge and unnecessary warning about mkdocs 2 incompatibility that feels somewhat FUD-driven.

#Mkdocs #MaterialForMkdocs #opensource

@squidfunk I used #MkDocs and #Material for a tiny project. Awesome resource: fast, elegant and easy to use (for a beginner like me).
@steff @sigmasternchen I'd do something like #MkDocs-Material likely just to have something useable and nice...

I've recently migrated a few (small) sites from #MkDocs (no longer maintained) to #Zensical, which went very smoothly.

It also motivated me to write a small Markdown extension for including source code for #Python functions, classes, methods, etc, similar to the `:pyobject:` option in reStructuredText's `literalinclude` directive:

https://includepy.readthedocs.io/en/latest/

(I'm aware of the snippets extension, which has many more features, but requires adding markers to the source files)

Get started - IncludePy

Include Python source code in Markdown files.