Login
You're viewing the discuss.systems public feed.
  • Jun 27, 2026, 9:21 AM

    Was surprised to see a rather "unusual" warning when running mkdocs build for a project.

    Can anybody (who knows the circumstances more deeply) summarize the #mkdocs vs #zensical drama? (the root causes, as seen by a dispassionate third party 😅 ).

    On the face of it is seems akin to the #wordpress #wpengine story, a conflict about money and control after an open source project becomes more widely adopted.

    Maybe I should have stayed with sphinx 😟

    │  ⚠  Warning from the Material for MkDocs team
 │
 │  MkDocs 2.0, the underlying framework of Material for MkDocs,
 │  will introduce backward-incompatible changes, including:
 │
 │  × All plugins will stop working – the plugin system has been removed
 │  × All theme overrides will break – the theming system has been rewritten
 │  × No migration path exists – existing projects cannot be upgraded
 │  × Closed contribution model – community members can't report bugs
 │  × Currently unlicensed – unsuitable for production use
    💬 0🔄 5⭐ 0