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.
I’ve been building online help since the early days — back when HTML ruled and editors were mainly plain text. Things have changed a lot, but some fundamentals are still going strong.
In this piece, I look back at how Help has evolved, from RoboHelp and tri-pane structures to the cleaner world of Markdown and static site generators. It’s part nostalgia, part practicality — and all about making documentation better.
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.
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.