Write, structure, and publish technical documentation in a visual editor with Markdown mode, AI-assisted edits, reusable components, and version history.
Hey Product Hunt, I’m Faizan, the founder of DocsAlot.
Almost everything in software is being rebuilt for agents right now. We’re doing that too: DocsAlot gives agents access to documentation through the CLI and MCP, and AI can help create and update the content.
But we kept running into one important truth: a human still needs to make the final call before documentation becomes public.
That is why we built this editor.
The technically difficult part wasn’t putting a text box in a browser. It was building a visual editing experience without breaking the underlying Markdown. A page can move between visual and source mode while preserving its frontmatter, tables, code, links, and structure.
We also separated editing from publishing. Changes live in a working draft. A human deliberately saves a version, can return to an earlier version, and chooses exactly when that version becomes the public site.
The navigation is treated as real site data too, so moving pages and groups updates the same structure used by the published documentation.
The result is a workflow where agents can do more of the work, but people remain in control of what readers actually see.
We’re launching the first complete version of that workflow today: pull, edit, save, and publish, from the visual editor, CLI, or MCP.
I’d love to hear how your team thinks about this balance. If an agent updates your docs, what would you need to see before you feel comfortable publishing the change?
About DocsAlot Visual Editor on Product Hunt
“Create beautiful docs, by typing. No AI required. ”
DocsAlot Visual Editor launched on Product Hunt on September 6th, 2026 and earned 185 upvotes and 15 comments, placing #5 on the daily leaderboard. Write, structure, and publish technical documentation in a visual editor with Markdown mode, AI-assisted edits, reusable components, and version history.
On the analytics side, DocsAlot Visual Editor competes within API, Writing and Developer Tools — topics that collectively have 676.8k followers on Product Hunt. The dashboard above tracks how DocsAlot Visual Editor performed against the three products that launched closest to it on the same day.
Who hunted DocsAlot Visual Editor?
DocsAlot Visual Editor was hunted by faizan khan. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Reviews
DocsAlot Visual Editor has received 1 review on Product Hunt with an average rating of 4.00/5. Read all reviews on Product Hunt.
For a complete overview of DocsAlot Visual Editor including community comment highlights and product details, visit the product overview.
faizan khan
Hey Product Hunt, I’m Faizan, the founder of DocsAlot.
Almost everything in software is being rebuilt for agents right now. We’re doing that too: DocsAlot gives agents access to documentation through the CLI and MCP, and AI can help create and update the content.
But we kept running into one important truth: a human still needs to make the final call before documentation becomes public.
That is why we built this editor.
The technically difficult part wasn’t putting a text box in a browser. It was building a visual editing experience without breaking the underlying Markdown. A page can move between visual and source mode while preserving its frontmatter, tables, code, links, and structure.
We also separated editing from publishing. Changes live in a working draft. A human deliberately saves a version, can return to an earlier version, and chooses exactly when that version becomes the public site.
The navigation is treated as real site data too, so moving pages and groups updates the same structure used by the published documentation.
The result is a workflow where agents can do more of the work, but people remain in control of what readers actually see.
We’re launching the first complete version of that workflow today: pull, edit, save, and publish, from the visual editor, CLI, or MCP.
I’d love to hear how your team thinks about this balance. If an agent updates your docs, what would you need to see before you feel comfortable publishing the change?