|
Introducing Zensical Studio |
|
|
Today, we're launching Zensical Studio, the missing productivity layer for Docs-as-Code. The idea is simple: Refactor documentation like code. When you rename, move, or restructure content, Zensical Studio keeps your links, headings, and references up to date – fast, reliable, and integrated with Visual Studio Code. |
|
Rename a heading in Zensical Studio – all incoming links are updated automatically.
|
|
Zensical Studio is in Public Beta. You can install it now from the Visual Studio Marketplace and get up and running in Visual Studio Code in minutes. |
|
|
Why we're building Zensical Studio |
Docs-as-Code has proven to be a powerful way to write and publish documentation, but the authoring experience has never really matched the workflow – to this day, teams assemble Markdown tooling from various sources themselves. None of these tools natively understand Python Markdown, which Zensical and MkDocs depend on. |
Zensical Studio closes that gap for Zensical and MkDocs projects: |
- [Broken links] are caught instantly, right in your editor
- Accurate Python Markdown highlighting, completions and navigation
- Safe renames of headings with incoming links updated automatically
- No new tools to learn – integrated with your existing workflow
|
What's next |
With Zensical Studio, we're building the integrated authoring experience for Docs-as-Code that users have long asked for – and that we've long wanted ourselves. |
Accurate Python Markdown support was the technical foundation Zensical Studio needed. Making it fast, reliable, and precise across real-world Zensical and MkDocs projects required substantial engineering effort. With that foundation in place, we're already working on the next set of capabilities: |
- Automatic formatting of Python Markdown
- Native support for topic-based authoring
- WYSIWYG editing for non-technical contributors
- Collaboration features for teams
- Custom validators for organizational standards and compliance
- Tooling for migrating from MkDocs
|
Our goal is to create a fully integrated and actively maintained stack for technical writing. By reducing the need to assemble and maintain many separate tools, Zensical Studio helps teams move faster with fewer moving parts, while lowering operational complexity and supply-chain risk. |
Your voice matters |
Zensical Studio is in Public Beta, and your feedback will help shape where it goes next. If you think you've discovered a bugs, please report it on GitHub as usual. If you have ideas, questions, or thoughts about the direction of Zensical Studio, we’d love to hear them – join the conversation on Discord, or simply reply to this email. |
We read everything. |
