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

@mgorny
Planning griffe2md + astro, but griffe2md needs some work for this
@mgorny Sphinx is rock solid, I agree, but the average level of themes available is very "old style"
@keul, who cares? It's fricking documentation, it's supposed to be readable, not fancy.
@mgorny I partially disagree, I'm not talk about shiny stuff, but useful stuff that are missing.
It has been ages before last time I build a new theme, but I can still recognize a sphinx theme (commonly: rtd or a theme based on rtd) at first glance.
One example? You'll never have a link to git repo or project website clearly visible. Never.
Same for highlighting some lines of code snippets, which is a super useful feature for building code tutorials.