DocsAlot

Name: DocsAlot
Rating: 4.0 (1 reviews)

Documentation that works for both humans and AI systems

4.0•1 review•

884 followers

Documentation that works for both humans and AI systems

4.0•1 review•

884 followers

Visit website

Knowledge base software

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

Launched this week

Create beautiful docs, by typing. No AI required.

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 tags:API•Writing•Developer Tools

Launch Team / Built With

Viktor.comAn AI coworker that actually does the work

Promoted

DocsAlot

Maker

📌

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?

Report

3d ago

Greplica

Totally what's needed.

How do you ensure stale context is not read?

Report

3d ago

Sourclip — Gemini Notebook Workspace

this is a pretty timely product. docs getting out of sync is already annoying , but having AI agents pull outdated or random context makes it even worse.

loved the idea of having the hosted docs, llms.txt, skill.md and MCP all coming from the same source instead of maintaining a bunch of separate layers.

Report

3d ago

Being able to review changes before publishing feels key for trust. Amazing work!

Report

2d ago

HarnessRouter

@new_user_2790a57d4d Congratulations. And happy product launch.

Report

3d ago

the markdown-preserving part is what I'd actually worry about breaking, tried building something similar once and the visual mode always mangled frontmatter or code blocks eventually. curious how long you've been dogfooding this on your own docs

Report

3d ago

DocsAlot

Maker

@wwenioaguiar for almost a year, this is indeed one of the most complex feature we have released. Do give it a shot, let me know if anything feels off.

Report

2d ago

A human gate catches formatting, it doesn't catch the failure that actually costs you, which is an agent writing a code sample that reads perfectly and doesn't run. Nobody rejects a diff that looks right. You already have the CLI, so the review step I'd want is mechanical: compile the snippets, check every endpoint mentioned against the OpenAPI spec, then show the human only the pages that failed. Approving 40 pages of prose is theatre, approving the 3 flagged ones isn't.

Report

2d ago

DocsAlot

Maker

@asadmalik901 love the idea asad, have you explored any solutions to these problems, what does your current workflow look like for this problem

Report

2d ago

@new_user_2790a57d4d Not solved, just contained. Every code sample in our docs is a real file in the repo with a test that runs it in CI, so a broken snippet fails the build instead of a reader. Prose is still unguarded and that's where the rot lives, renamed endpoints and screenshots from two versions ago. The check I actually want is docs diffed against the OpenAPI spec on every merge, and we haven't built it.

Report

2d ago

DocsAlot

Maker

@asadmalik901 we have an OpenAPI spec checker integrated into the dashboard, happy to give you a demo,

https://cal.com/faizan-khan-18shuq/30min

Report

1d ago

1 2

Previous DocsAlot Launches

DocsAlot CLILet Claude or Codex create and maintain good looking docs

Launched on August 9th, 2026

DocsAlotDocumentation that works for both humans and AI systems

Launched on July 5th, 2026

Hey Product Hunt, I’m Faizan, the founder of DocsAlot.

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 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?

DocsAlot

Documentation that works for both humans and AI systems

Documentation that works for both humans and AI systems

DocsAlot Visual Editor

Previous DocsAlot Launches

Previous DocsAlot Launches

What's great

What needs improvement

vs Alternatives

What's great

What needs improvement

vs Alternatives