Skip to content
The Docs Report
Tuesday, September 29, 2026NewsletterRSS

Zensical Clears Three Migration Blockers for Material for MkDocs Sites

In three releases from Sept. 22 to Sept. 28, Zensical added a native blog, RSS and JSON feeds, and Python API reference plugins.

3 min read

ZensicalOpen sourceMkDocs

Product photo of a closed cardboard moving box on a hot pink, magenta and orange gradient

Zensical, the successor to Material for MkDocs, now ships a native blog, RSS and JSON feeds, and support for two Python API reference plugins. All three arrived in releases between Sept. 22 and Sept. 28, six weeks before the project starts its stable 0.1 line on Nov. 5. The blog came first, in version 0.0.64 on Sept. 22.

The blog is a straight port

Zensical’s blog is a direct port of the Material for MkDocs blog plugin, so existing blog setups should carry over unchanged. “As a direct port of the Material for MkDocs blog plugin, it preserves the familiar configuration, metadata, URLs, archives, categories, authors, pagination, and more,” the Zensical team wrote in the Sept. 22 release notes. The setup docs, updated the same day, say it reads both blog and material/blog plugin entries, the default blog/ folder and .authors.yml, and that “no additional plugin package needs to be installed.”

The request had been open in Zensical’s public backlog since Nov. 13, 2025, and was closed on Sept. 22. One gap remains: the compatibility docs say custom Python callables aren’t supported, only the built-in strategies. The team said more flexible blogging “designed specifically for Zensical” is planned.

Version 0.0.65, released Sept. 24, replaces the rss plugin with native RSS 2.0 and JSON Feed 1.1 output for created and updated pages. It also adds mkdocstrings backlinks and reads more settings from mike, mkdocstrings, autorefs and macros. The compatibility docs list what it skips: cache_dir, remote images for feed enclosures and use_material_social_cards.

API reference pages build themselves

Version 0.0.66, released Sept. 28, works with mkdocs-autoapi and mkdocs-api-autonav, which scan a Python package and generate one reference page per module. The release notes say this means teams can “skip manually creating a page for each module.” Both plugins need a nonempty relative subdirectory as their output root, and discovery always skips .git, .venv, venv and __pycache__. The same release fixes sitemaps that left out published pages.

What comes next

Zensical 0.1.0 is due Nov. 5, according to a page the project published this month. That page says about 84,000 public GitHub repositories depend on Material for MkDocs, which now receives critical fixes only, through May 5, 2027. “No forced migration. Existing projects will continue to work,” it says. Zensical is MIT-licensed, and the page says the project does not charge “for sites, readers, builds, publishing, deployment, or access to your content.” Paid plans cover its hosted Studio product.

Key takeaways

  • Zensical 0.0.64 ports the Material for MkDocs blog with the same configuration and URLs.
  • Version 0.0.65 adds RSS 2.0 and JSON Feed 1.1 and mkdocstrings backlinks.
  • Version 0.0.66 generates Python API reference pages through mkdocs-autoapi and mkdocs-api-autonav.
  • The stable 0.1 line starts Nov. 5; Material for MkDocs gets critical fixes through May 5, 2027.

The take

We think this was Zensical’s most important week of the year. Until now, a site with a blog, a feed or generated API pages had a reason to stay on Material for MkDocs, and those reasons are gone six weeks before the stable line starts. Porting the blog as-is rather than redesigning it was the right call, because teams can switch first and pick up new features later. We’d still run a test build before Nov. 5. The list of ignored settings is short, and a team that relies on custom Python callables or social cards in feeds will run into it.