Mkdocs state

[xvik]

Mkdocs developer stopped mkdocs 1.x maintenance (one, two)
and did a complete rewrite: mkdocs 2.0 (pre-release)
is not backwards compatible and completely breaks ecosystem (plugins).

Because of this, mkdocs-material developers stopped development
(only critical bug fixes until November 2026). In short, forking was not an option because plugins
depend on mkdocs dependency, so they decided to create a completely new tool Zensical
(alpha state; compatibility with mkdocs-material is a top priority).

But the mkdocs community is strong, so we also have two maintained forks for mkdocs and mkdocs-material:

• ProperDocs with materialx
• mkdocs-ng (material inside) (why another fork)

No need to panic. As you can see, we have options to migrate. Also, the current
mkdocs release could be used for years ahead.

The plugin state

I'm going to release the plugin with updated defaults (latest mkdocs and material) which could
be used for years (python backwards compatibility is quite good).

Also, I'm going to add an option to switch to materialx
(two sets of defaults and, probably, initial templates), so we could have an
easy migration, if required. The migration process would be documented.

Zensical is in too early stage, so just waiting for its evolution. When it matures and
becomes a good enough alternative, a new plugin could be created (we'll see).

No panic, no worries! Beautiful documentation is still with us.

Any ideas, thoughts or news are welcome!