Visual documentation editor

A visual docs editor with Markdown underneath.

Write technical documentation in the browser without turning the source into a black box. DocsAlot combines visual editing, Markdown control, AI-assisted changes, page structure, and versioned publishing in one workspace.

Try the editor →See how it works ↓
  • Visual and Markdown modes
  • Technical content blocks
  • Review before publishing
DAcme API docsProduction workspace
All changes saved PreviewPublish
Visual Markdown
Getting startedAuthentication
Paragraph

Guide

Authenticate API requests

Use a workspace API key to authenticate server-side requests. Keep the key outside your repository and send it in the authorization header.

Before you beginCreate a restricted key for each production environment.

Send your first authenticated request

cURLCopy
curl https://api.acme.dev/v1/projects \
  -H "Authorization: Bearer $ACME_API_KEY"

Visual when it helps. Source when it matters.

Use the writing surface that fits the change.

Product and support teams can edit a guide without memorizing Markdown syntax. Developers can switch to source mode for exact control. Both views change the same content, so the team does not have to choose between usability and portability.

See the GitHub docs workflow
Visual Markdown
Quickstart

Create your first project

Set up a workspace, create an API key, and make your first request.

Keep production keys in your secret manager, not in the repository.
---
title: Create your first project
description: Set up a workspace...
---

# Create your first project

Set up a workspace, create an API key, and make your first request.

<Callout type="info">
Keep production keys in your secret manager.
</Callout>

AI that edits the documentation

Ask for an outcome, then inspect the work.

The AI assistant works inside the documentation workspace rather than in a separate chat box. Ask it to improve one explanation, update related pages, or use product context to repair a weak onboarding path. You still decide what gets published.

Build AI-readable documentation
authentication.mdx

Authenticate requests

Send your key in the authorization header for every server-side request.

Use a separate restricted key for each environment and rotate it without changing application code.

DocsAlot AI
Make this safer and update the request example too.
Read the current guide
Checked related pages
Proposed 2 edits
authentication.mdx
first-request.mdx

A deliberate publishing path

Fast editing does not have to mean accidental publishing.

DocsAlot separates the draft from the public site. Save a version, preview the result, validate the navigation, and publish when the documentation is ready. Version history gives the team a clear record of what changed.

Open the published DocsAlot example
Release workflowAuthentication refresh
Ready to publish
1Edit

Write visually, in Markdown, or with AI.

2Review

Preview the version and inspect each change.

3Publish

Move the approved version to the public docs.

Technical content should feel native in the editor.

A generic rich-text editor stops being useful as soon as a guide needs working code, structured steps, reusable callouts, or API context. DocsAlot treats those patterns as normal documentation building blocks.

Code groups

Keep examples readable across languages.

Callouts

Separate warnings, context, and next steps.

Steps

Turn setup work into a clear sequence.

Tables

Edit structured reference content visually.

Tabs and cards

Organize choices without duplicating pages.

Evaluate the wider system

The editor is one part of a useful docs stack.

See how the writing workflow connects to AI readability, publishing quality, and the tools teams often compare before they choose a documentation platform.

AI-readable documentationKeep human and agent-facing outputs attached to the same source.
Public docs benchmarkSee how real documentation performs across discoverability and usability checks.
GitBook alternativeCompare editor, automation, AI-readability, and operating-model fit.
ReadMe alternativeCompare visual editing with the rest of the API documentation workflow.

Visual editor questions

What teams usually ask.

What is a WYSIWYG documentation editor?

A WYSIWYG documentation editor shows the formatted page while you write it, so headings, links, callouts, code, tables, and other components look close to the published result. DocsAlot also keeps Markdown mode available for source-level control.

Can developers edit the Markdown directly?

Yes. Visual mode and Markdown mode work on the same page content. Contributors can use the visual editor for routine changes and switch to Markdown when they need precise control over technical syntax or page metadata.

Can the AI editor update more than one documentation page?

The DocsAlot assistant can work with the wider documentation set, propose changes across relevant files, and show which pages changed before the team publishes a new version.

Does saving a draft immediately change the public docs?

No. Editing and publishing are separate steps. Teams can review a saved version, preview the result, and publish deliberately when the documentation is ready.

Start with the page in front of you

Write the docs without fighting the editor.

Use visual mode for speed, Markdown for precision, and AI when the change needs more context than a single paragraph.

Try the editor →See pricing →