Zensical 0.1.0: one year in, and we're just getting started
Exactly one year ago today, we released the first version of Zensical. Today, Zensical reaches its 0.1.0 milestone.
This release closes the major remaining compatibility gaps with MkDocs, including support for many of its most widely used plugins. You can bring your existing MkDocs project to Zensical and continue using the workflows you're familiar with.
With 0.1.0, Zensical enters beta for the next three months. Thousands of projects already use it, and we expect it to work reliably in production. The beta period gives us time to gather feedback, address remaining issues, and continue refining the APIs and ecosystem. If all goes as expected, we plan to move to stable after those three months.
MkDocs compatibility has been essential to giving existing projects a path forward. It also gives us a foundation for what comes next. Our ambition is to build Zensical into a broader system for technical content: one that helps teams create, maintain, and publish across channels.
Studio brings project understanding into the editor, helping you work with connected content. Spark brings practitioners and organizations closer to our work and gives them a voice in Zensical's direction. Both are optional, and they help sustain the team behind Zensical. Zensical is and will always be free.
Thank you to everyone who has tried Zensical, reported issues, contributed, or shared what they need. This is the beginning of a much longer journey, and we're excited to build what comes next together.
Changelog
Bug fixes
- 340c3ac – update vulnerable dependencies
- d6fdf6e zensical, compat – preserve configured and inherited static templates
- 0d8201a zensical, compat – validate MkDocs-compatible configuration before building
- 3acbefe zensical, compat – align extra template paths and warnings with MkDocs
- 1ccc67a zensical, compat – match MkDocs extra script module inference
- ab99f8f zensical, compat – align approved MkDocs URL configuration and page links