Skip to content

2026

Shift-Left to the Keystroke: The Zenzic VS Code Extension

Architectural Update

Historical Note: This post refers to Zenzic as a "linter". As the system evolved, its capabilities expanded far beyond surface-level linting. Zenzic is now officially classified as a Deterministic Document Integrity Engine for Markdown/MDX graphs. Read the latest documentation for current architectural capabilities.

Since its inception, Zenzic has operated as a strict, deterministic gatekeeper for CI/CD pipelines. It ensures that no broken links, malformed topology, or hardcoded credentials ever reach production.

Today, we are eliminating the latency between authoring a defect and discovering it. We are officially releasing the Zenzic VS Code Extension, bringing the deterministic precision of our engine directly into your authoring environment.

Zenzic v0.20.0: The Extensibility Update — Custom AST Rules & Auto-Fix Expansion

Architectural Update

Historical Note: This post refers to Zenzic as a "linter". As the system evolved, its capabilities expanded far beyond surface-level linting. Zenzic is now officially classified as a Deterministic Document Integrity Engine for Markdown/MDX graphs. Read the latest documentation for current architectural capabilities.

Zenzic v0.20.0 is the first release to expose the engine's internal Abstract Syntax Tree to the outside world. After v0.19.0 laid the AST foundations, The Extensibility Update answers a long-standing question: what if the rules I need simply don't exist yet?

With v0.20.0, you write them yourself — in plain Python, in under a minute, with zero packaging.

Zenzic v0.19.0: The AST Foundations & Atomic Auto-Fix

Zenzic v0.19.0 is arguably the most significant structural milestone for the engine since its inception. Until today, Zenzic operated entirely as a read-only static analyzer, relying on heavily optimized regular expressions to validate Markdown. With v0.19.0, we have laid the architectural foundation for a new era of document mutation and auto-fixing.

This release represents a fundamental shift in how Zenzic understands and interacts with Markdown content.

10 Documentation Bugs Caught by Zenzic

Documentation isn't just text — it's a critical interface. When users rely on your docs to deploy infrastructure, configure security policies, or integrate APIs, a "simple typo" can lead to hours of lost productivity.

In a docs-as-code workflow, documentation is code. And just like code, it has bugs. That's why we built Zenzic: a Deterministic Document Integrity Engine for Markdown/MDX graphs.

Here are 10 subtle, frustrating, and downright dangerous documentation bugs that Zenzic catches automatically in your CI/CD pipelines.

Zenzic v0.17.0: HTML Validation in Markdown Documents

With the release of Zenzic v0.17.0, Zenzic expands its validation capabilities beyond Markdown syntax. In addition to Markdown links and assets, Zenzic can now analyze raw HTML references embedded in Markdown documents.

A common limitation of Markdown-focused tooling is that raw HTML embedded inside Markdown documents is not analyzed with the same rigor as native Markdown constructs. When developers embed anchor or image elements directly into their Markdown for custom layouts, broken links and missing assets can remain undetected.

With v0.17.0, HTML links and images are analyzed by the same validation pipeline used for Markdown references.

  • 6 min read

Zenzic v0.16.0: Engineering Determinism into Documentation Pipelines

Zenzic v0.16.0 marks the transition from an experimental toolchain to production infrastructure. The changes in this release address three classes of problems that accumulate silently in long-running documentation pipelines: malformed configuration that allows analysis to start on an invalid basis, unused allowlist entries that widen the security perimeter without purpose, and inconsistent exception types that force CI adapters to implement defensive workarounds.

  • 6 min read

Why We Dropped Docusaurus: The Ontological Limits of Static Analysis

Architectural Update

Historical Note: This post refers to Zenzic as a "linter". As the system evolved, its capabilities expanded far beyond surface-level linting. Zenzic is now officially classified as a Deterministic Document Integrity Engine for Markdown/MDX graphs. Read the latest documentation for current architectural capabilities.

We spent a full development cycle building a Docusaurus adapter for Zenzic. We ran forensic audits on real Docusaurus projects. Then we deleted every line of it.

  • 4 min read

Auditing the Auditors: Finding Documentation Defects with AST-Based Analysis

Architectural Update

Historical Note: This post refers to Zenzic as a "linter". As the system evolved, its capabilities expanded far beyond surface-level linting. Zenzic is now officially classified as a Deterministic Document Integrity Engine for Markdown/MDX graphs. Read the latest documentation for current architectural capabilities.

To validate the parser and snippet-analysis capabilities of Zenzic, we needed a production-grade documentation corpus. We selected the official documentation repository of Zensical, a mature and actively maintained static site generator.

The expectation was straightforward: a well-maintained documentation codebase should produce few, if any, actionable findings.

Instead, the scan surfaced a small set of defects that had survived normal review processes. None were catastrophic, but all had user-facing consequences ranging from copy-paste failures to broken navigation and accessibility regressions.

This article examines the findings and explores why documentation quality often requires deeper analysis than conventional Markdown validation.

  • 3 min read

Zenzic v0.10.0: Async Engine, Native Annotations, and Progressive Adoption

Architectural Update

Historical Note: This post refers to Zenzic as a "linter". As the system evolved, its capabilities expanded far beyond surface-level linting. Zenzic is now officially classified as a Deterministic Document Integrity Engine for Markdown/MDX graphs. Read the latest documentation for current architectural capabilities.

Zenzic v0.10.0 introduces a massive performance upgrade with a new Async Network Engine, alongside two architectural changes designed strictly for the CI/CD pipeline: Native GitHub Annotations and Destructive Rule Filtering.

These features are not aesthetic. They are built to solve three specific operational bottlenecks: network-induced CI flakiness, context switching during Pull Request reviews, and the high friction of adopting static analysis in legacy documentation repositories.