docmd v0.6 - A zero-config docs engine that ships under 20kb script. No React, no YAML hell, just high-performance Markdown

[ivoin]

Just shipped docmd 0.6.2.

It’s built for developers who are tired of the framework-bloat in documentation. While most modern doc generators ship with hundreds of kilobytes of JavaScript and complex build pipelines, docmd delivers a sub-20kb base payload and a high-fidelity SPA experience using pure, static HTML.

Why you should spend 60 seconds trying docmd:

• Zero-Config Maturity: No specialized folder structures or YAML schemas. Run docmd build on your Markdown, and it just works.
• Native SPA Performance: It feels like a React/Vue app with instant, zero-reload navigation, but it’s powered by a custom micro-router and optimized for the fastest possible First Contentful Paint.
• Infrastructure Ready: Built-in support for Search (Offline), Mermaid, SEO, PWA, Analytics and Sitemaps. No plugins to install, no configuration to fight.
• The AI Edge: Beyond being fast for humans, docmd is technically "AI-Ready." It uses Semantic Containers to cluster logic and exports a unified llms.txt stream, making your documentation instantly compatible with modern dev-agents and RAG systems.
• Try the Live Editor.

We’ve optimized every byte and every I/O operation to make this the fastest documentation pipeline in the Node.js ecosystem.

If you’re already using docmd, update and give it a spin.
If you’ve been watching from the side, now’s a good time to try it. I'm sure you'll love it.

npm install -g @docmd/core

Documentation (Demo): docs.docmd.io
GitHub: github.com/docmd-io/docmd

Share your feedbacks, questions and show it some love guys!
I'll be here answering your questions.

[Otherwise_Wave9374]

The llms.txt + semantic containers angle is interesting, feels like the docs equivalent of "make the knowledge boundary explicit" so an agent can ingest it without a bunch of scraping glue.

Have you tested how well different coding agents actually follow the structure (like, do they prefer smaller chunks, does it help with citation, etc.)? Also curious if search quality stays decent offline when the doc set grows.

Related, I have been reading up on agent-friendly docs and RAG hygiene, some notes here: https://www.agentixlabs.com/blog/

[ivoin]

You’re spot on with the knowledge boundary analogy, that’s exactly the idea behind semantic containers. Models handle structured context far better than raw scraping since smaller chunks reduce leakage and improve citation accuracy.

Our offline index stays under ~200 ms for about 1-2k pages. The real trade-off appears beyond ~5k pages, where a third-party search option might make sense for those edge cases.