ReplayAutonomous app testing for teams who ship at AI-speed
Promoted
DocsAlot turns scattered help center articles, knowledge base, and developer docs into one source of truth for humans and AI agents. It includes hosted MCP, llms.txt, and skill.md. Your docs show up in AI answers, onboarding gets faster, and agents stop reading stale context.
This is the 3rd launch from DocsAlot. View more
DocsAlot Visual Editor
Launching today
Write, structure, and publish technical documentation in a visual editor with Markdown mode, AI-assisted edits, reusable components, and version history.
Interactive
Payment Required
Launch Team / Built With
Mintlify
DocsAlot
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?
HarnessRouter
@new_user_2790a57d4d Congratulations. And happy product launch.
Softorino 💻📲
Writing help docs, the useful bit is the step someone got stuck on. Typing it yourself is the only way that detail survives into the page.
Dial
the human-approval gate before publishing makes sense. what happens on the other side of that though - if an agent proposes a doc update through the CLI/MCP and a human edits or rejects most of it before saving, does the agent see what changed and why, or does it just try again from scratch next time with no memory of the correction?