docmd Review: No React, Zero Config, Production Docs from Markdown in Seconds

Choosing a documentation tool has always been a trade-off. Docusaurus and VitePress are full-featured but not lightweight to configure. GitBook and Notion are convenient but hosted on someone else’s platform with limited customization. Writing raw HTML is too primitive.

I recently discovered docmd, a documentation generator with the tagline “No React, no bloat, just content.” 1.4k stars, written in TypeScript. It claims to generate production-ready docs from Markdown in seconds — and after trying it, that’s basically accurate.

What problem does it solve

docmd’s positioning is clear: you write Markdown, it handles everything else.

No webpack configuration, no React components, no theme CSS tweaking, not even node_modules needed (single-file executable). Feed it a Markdown file, get a deployable documentation site.

This hits a pain point for many people — especially those in the “I just want to write README-level docs without setting up a documentation engineering pipeline” category.

Core features in practice

Zero-config startup The most appealing feature. npx docmd README.md generates a complete documentation site. No docmd.config.js, no _sidebar.md, no prerequisites. The default styling already looks good — typography, code highlighting, navigation, all included.

Theme system Despite being zero-config, it offers theme support. Several built-in themes (light, dark, slate, etc.) via the --theme flag. Themes aren’t just color swaps — they adjust the overall visual style including font pairing, spacing rhythm, and border treatment. I tried the slate theme and the quality is solid.

Plugin extensions A simple plugin system extends Markdown rendering behavior. I installed a mermaid plugin, and mermaid code blocks in my docs rendered as flowcharts directly. Plugins are npm packages — install and use.

Container support An official Docker image lets you run it in one command: docker run -v $(pwd):/docs docmd/docmd README.md. CI/CD friendly — call the container in GitHub Actions to generate and deploy docs.

Search functionality Generated sites include full-text search based on real-time content indexing. The search box sits in the top-right corner, entering keywords quickly locates relevant sections. No need to integrate Algolia or third-party services — works out of the box.

Real usage scenarios

Scenario 1: Quick product docs Our small team built an internal tool and needed a simple usage guide. We converted the README with docmd, added a custom domain, done in ten minutes. More professional than a Notion public page, less work than setting up Docusaurus.

Scenario 2: API documentation Pair with API doc generation tools (like those that generate Markdown from OpenAPI specs), then convert to a site with docmd. The pipeline is smooth and the end result is sufficient. Of course, for large API platforms, you’d probably still want Swagger UI or dedicated API doc platforms.

Scenario 3: Personal knowledge base String together scattered Markdown notes into a site with docmd, deploy locally or on a VPS. Cheaper than Obsidian Publish (free), simpler than Hexo/Hugo.

Quick start

# Single-file generation (simplest approach)
npx docmd README.md

# Specify output directory
npx docmd docs/ --output dist/

# Switch theme
npx docmd README.md --theme dark

# Use plugins (mermaid example)
npm install docmd-plugin-mermaid
npx docmd README.md --plugins mermaid

# Docker approach
docker run -v $(pwd):/docs docmd/docmd README.md

The good and the bad

What I loved:

• Zero-config startup is not a gimmick — one command actually works
• Default styling looks good, not the “functional but ugly” default theme
• Single-file execution (npx directly), no project init, no dependency installation
• Generated sites are pure static HTML, deployable anywhere
• Plugin system is nicely restrained, core functionality stays lean

What frustrated me:

• At 1.4k stars it’s still a small project, ecosystem and plugins far behind Docusaurus/VitePress
• Multi-language support is basic, no built-in i18n solution
• Custom themes require writing CSS, no component-level override like Docusaurus
• Navigation structure is file-directory based, limited support for complex document hierarchies
• No built-in version management (multi-version docs), a dealbreaker for SDK documentation

Compared to alternatives

Tool	Pros	Cons	Best for
docmd	Minimal, zero-config, fast	Fewer features, small ecosystem	Lightweight docs, quick starts
Docusaurus	Full-featured, large ecosystem, extensible	Complex config, heavy deps	Large project docs, complex needs
VitePress	Fast, Vue ecosystem	Requires config, needs Vue knowledge	Vue project docs, tech blogs
GitBook	Online editing, collaboration	Third-party hosted, paid	Team collaboration, non-technical

My recommendation: if you just want to quickly set up a clean product docs site without fiddling with configuration, docmd is a great choice. If your docs needs are complex (versions, languages, deep customization), you’ll still need Docusaurus or VitePress.

Bottom line

docmd is one of those “small but beautiful” tools, and 1.4k stars shows it found its audience. It doesn’t try to compete with Docusaurus on feature richness, but instead optimizes the “Markdown to docs site” pipeline for extreme simplicity and speed.

For indie developers, small teams, or anyone who temporarily needs a docs page, the time docmd saves might be more valuable than the advanced features it’s missing. Because often, what we need isn’t a documentation platform — we just want our Markdown to look good.

---

About the Author

Liudingyu is a full-stack developer and heavy GitHub user. With 900+ starred repos over the past 3 years, this site only covers tools I’ve actually used or deeply researched.

📧 Found a great tool to recommend? Email [email protected]