Forem: Adam Makins

[Boost]

Adam Makins — Thu, 07 May 2026 13:48:20 +0000

Adam Makins

May 7

Why Your Documentation Doesn't Need React, Meet docmd 0.7.9

#ai #webdev #productivity #javascript

Comments

2 min read

Why Your Documentation Doesn't Need React, Meet docmd 0.7.9

Adam Makins — Thu, 07 May 2026 13:47:25 +0000

Documentation has become bloated. In a world where we just want to turn Markdown into a production-ready site, we often find ourselves wrestling with React components, complex CI/CD pipelines, and heavy JavaScript bundles that slow down the user experience and confuse AI crawlers.

Today, we’re releasing docmd v0.7.9, moving closer to our goal of providing a "Gold Standard" for technical documentation that is fast, private, and AI-ready by default.

1. Static OpenAPI Rendering (No more Swagger bloat)

The headline feature of 0.7.9 is our new OpenAPI plugin. Unlike traditional tools that load a massive JS bundle to render your API spec, Docmd reads your openapi.json at build-time and generates semantic HTML.

Zero Runtime JS: Instant page loads.
SEO & AI Friendly: Every endpoint is indexed as static text.
Native Look: API docs that actually match your site’s theme.

2. Documentation for the AI Era

We believe documentation should be as easy for LLMs to read as it is for humans. Docmd automatically generates llms.txt and llms-full.txt (via @docmd/plugin-llms), providing a high-signal stream of your entire project context. In 0.7.9, we've refined how code blocks and diagrams are presented in these streams to reduce AI hallucinations.

3. Git-Powered Intelligence

The @docmd/plugin-git is now a core feature. It automatically injects "Last updated" timestamps and contributor history tooltips by reading your repository’s local history. No manual "lastModified" fields required.

4. The Developer Experience (TUI)

We’ve spent time refining the Terminal UI. When you run docmd build, you get a clean, emoji-free, professional interface that keeps you informed without the clutter.

The Roadmap to 0.8.0

As we approach our next major milestone, we are focusing on:

Plugin Capability Enforcement: Hard boundaries for core and community plugins.
Enhanced Localisation: Deeper support for Right-to-Left (RTL) languages.
Advanced Search: Boosting search relevancy using local vector-like scoring.

If you’re tired of documentation tools that feel like full-blown web frameworks, give docmd a try.

npx @docmd/core build — That’s all it takes.

Check release note for 0.7.9 release.

Complete docmd documentation.

Give it a try.

Adam Makins — Wed, 18 Feb 2026 06:54:54 +0000

Is docmd the fastest way to ship docs? An honest look at the new v0.4 release.

Adam Makins ・ Feb 18

#node #javascript #webdev #productivity

Is docmd the fastest way to ship docs? An honest look at the new v0.4 release.

Adam Makins — Wed, 18 Feb 2026 06:50:50 +0000

We are spoiled for choice with documentation generators. Docusaurus, MkDocs, VitePress... do we really need another one?

I recently took docmd (specifically the new v0.4.0 monorepo release) for a spin to document a small Node.js library. The promise is "Zero Config" and "Static HTML."

Here is my honest take on where it shines, where it falls short, and who should use it.

👍🏼 The Good Stuff

1. Actually Zero Config
You run docmd init, then docmd build. That’s it. You get a site/ folder ready for Netlify or GitHub Pages. There is no complex config file unless you want to change defaults.

2. The "Live" Architecture
This is the coolest technical feature. Because the core engine is isomorphic, the docmd live command opens a browser-based editor that renders changes instantly. It doesn't feel like a "hot reload" (which takes 500ms+); it feels like typing in a native app.

3. Built-in Offline Search
Most static site generators force you to set up Algolia DocSearch. That involves applying for an account, setting up API keys, and configuring CI crawlers.
docmd generates a search-index.json locally. Search works out of the box, is privacy-friendly, and works offline.

4. AI Readiness
It automatically generates an llms.txt file. If you use tools like Cursor or ChatGPT to query your own docs, this is a massive quality-of-life feature that I haven't seen standard in other tools yet.

👎🏼 The "Fallbacks" (Areas for Improvement)

1. No MDX (Yet)
If you are coming from Docusaurus, you might be used to importing React components directly into your Markdown files (MDX). docmd is strict Markdown + HTML. You cannot import a <Counter /> component. If you need complex interactivity inside your docs, stick to React-based generators.

2. Theming Limitations
The built-in themes (Sky, Retro, Ruby) are nice, and you can inject custom CSS. But there isn't any robust "Theme Builder" UI yet. If you want to drastically change the layout (e.g., move the sidebar to the right), you'll be writing raw CSS overrides.

3. Ecosystem Size
It’s a newer tool. The plugin system is fresh (from what I see, just recently introduced in v0.4+). While it has the essentials (SEO, Analytics, Mermaid, Sitemap), it doesn't have the massive plugin library of MkDocs or Gatsby, although it's a little early to say how the whole ecosystem evolves.

😇 My Opinion

docmd has carved out a specific niche: Performance and Simplicity.

Use docmd if: You are a library author, you hate configuring build tools, or you want a site that loads instantly on 3G networks because it sends zero JavaScript bloat to the client.
Stick to Docusaurus if: You are building a massive enterprise site that needs versioning dropdowns for 10 different software versions, or if you need MDX interactivity.

For my personal projects and NPM packages? I’m switching to docmd. The speed of the workflow is just addictive.

If you want to give it a go:
https://docmd.io

[Boost]

Adam Makins — Mon, 16 Feb 2026 06:58:25 +0000

Why I rewrote my CLI tool into an Isomorphic Monorepo

Ghazi ・ Feb 16

#webdev #javascript #productivity #opensource