Documentation is a product decision
Why I treat docs as part of the product — and what this space is for.
Welcome. I’m Ahamed Rasel, and this is where I write about the craft I spend my days on: turning complex software into documentation people can actually finish.
Here’s the belief that shapes everything I do — documentation is a product decision, not an afterthought. The docs are where a user meets your product without a salesperson in the room. They decide whether someone adopts a feature or files a ticket, whether they trust you or bounce. That’s not “content.” That’s product.
I lead the knowledge base for WPManageNinja’s Fluent plugin suite — tools running on 1.47M+ WordPress sites. At that scale, keeping docs accurate by hand is a race you lose. So I do two things at once: I write clearly, and I build the AI agents and n8n workflows that keep the writing honest as the product moves.
What I’ll write about here
- Docs as product — information architecture, release notes, and writing that reduces support load.
- AI workflows & agents — how I use Claude, Codex, and n8n to draft, review, and audit documentation at scale.
- Prompt engineering — what actually works when you put an LLM inside a real production pipeline.
- Field notes — the messy, specific lessons that don’t make it into polished guides.
Less theory, more of what I’ve actually shipped and broken. More soon.