4 posts tagged with "Docs-as-code"

The 2026 Toolset for Docs‑as‑Code and AI‑Friendly Technical Writers

In the age of AI, docs‑as‑code isn't a technical choice. It's a strategic one.

AI is advancing at an incredible pace. After agents, skills, and BMAD approaches, one thing has become clear: AI performs best when it works with clear structures, versioned data, textual content, and contextual information. In other words: the natural terrain of code.

That's exactly why documentation must now be treated like code.

Markdown, Docusaurus & Diagrams — My Happy Trio for Docs

A while back, someone asked me what tool I use for technical documentation — and instead of picking just one, I realized my setup is more of a creative trio.
I write in Markdown, build with Docusaurus, and sketch with Excalidraw. In this post, I'll share why this combo works so well for me and how it keeps writing both simple and powerful.

The Docs-as-Code Way: A Philosophy That Builds Better Docs

For years, documentation happened only after development was finished. The method involved gathering information — sometimes straight from developers, but mostly within our own bubble, working among technical writers. Then one day, I realized something: I was using Git, writing in Markdown, pushing commits, editing in VS Code. Wait a minute — I was doing docs-as-code.

Migrating with Confidence: From Hugo to Docusaurus V2

This summer, I dove back into a client's documentation with a dual mission: explain their new API and migrate the entire site to Docusaurus V2.
From search engines to stylish admonitions and ReDoc integration, this version doesn't just look good — it works brilliantly. Here's what we gained, and what to watch out for.