A first look at the new Spark

This month, we give you a first look at the new Spark experience, launching together with Spark Community on November 5. Right now, we're rebuilding Spark to achieve the shortest possible feedback loops, so we can deliver exactly what you need as fast as possible – drawing on more than a decade of Open Source experience.

We're also making Studio's workspace intelligence accessible to your agents, so they can understand your project, help you iterate, and fix broken links reliably. Additionally, we've kept working on MkDocs compatibility, with 11 more plugin replacements now available, including blog and social. Read on to learn more.

Where Spark is headed

Here's a first look at how we're bringing early releases and the conversations that shape them together in Spark, so you can share feedback directly.

Many companies sell software and offer a free forum for users to help each other. Our model is the other way around: Zensical is free and Open Source, and Spark is a paid community for developing it together with us. Your membership funds the time we spend solving problems with you, developing new features, and turning your feedback into better, free software. GitHub issues remain the right place for public bug reports and change requests, and Discord remains our community-led chat.

Spark Community launches for individuals on November 5, giving you early access to the latest Zensical features. You can use them months before public release and refine them with us, so what we ship reflects how you actually work.

For organizations, Spark gives your team a direct working relationship with us to keep migrations and rollouts moving. When questions or technical problems hold up your work, we help you resolve them, with defined response times for support requests.

See the membership benefits for details.

Agentic workflows with Studio

An agent can change a heading and leave broken links across hundreds of files. It has to search for and update every incoming link. Our tests show that agents sometimes miss them. Moving a page also means updating navigation, redirects, and includes.

That's why we're making Studio available as a tool for agents to understand your project and edit reliably. Across repeated runs, Studio consistently kept references in sync. In a test project with 2,400 Markdown files, an agent changed a heading with one tool call, and Studio adjusted hundreds of references.

Studio also repairs broken links after folder moves: the agent chooses the destination, and Studio applies and verifies the repairs. We tested the same agents on the same editing tasks, with and without Studio:

Tests covered projects with 24, 240, and 2,400 Markdown files. The agent handles the writing and decisions. Studio handles the project-wide consequences.

Studio Pro takes care of project-wide refactoring for both you and your agents. Compare editions and reserve an individual plan at reduced early supporter prices:

Plus applicable tax. No charge before November 5; you keep that price for as long as you remain subscribed. Studio Team launches for organizations on November 5.

11 new MkDocs plugin replacements

Across several Zensical releases, we shipped built-in plugin replacements for blog, social, and llmstxt, alongside api-autonav, audio, autoapi, callouts, exclude, gh-admonitions, rss, and video. If you use these plugins in your MkDocs projects, Zensical's built-in replacements should work with your existing configuration. See the compatibility guide and compatibility roadmap for more.

In other news

Your voice matters

With many popular MkDocs plugins covered, most projects can now move to Zensical. Now we're going beyond compatibility: designing modules that combine and extend those capabilities, built to work together from the start. Versioning, internationalization, and API documentation are a few examples on our roadmap.

Spark will be central to that work. Among the first features we'll release in Spark for early access are our 50x faster Markdown parser and the Module API for Python, so we can refine both with you before public release.

And as always, if you have questions or thoughts about where we're headed, simply reply to this email – we read everything.