Documentation automation

Turn product changes into docs updates.

Bring a release note and the article it affects. Draft the new instructions with an AI assistant, review what changed, and publish when the steps are right.

No credit card required.

Example of a release note and the resulting edit

Release note

Invoice downloads moved from Billing to the new Invoices tab.

Proposed edit to “Download an invoice”

Before — Go to Settings → Billing to download an invoice.

After — Go to Settings → Invoices. Open an invoice and select Download PDF.

Try it with your own content.

  1. Bring one change

    Start from an existing article or create a draft in your editor workspace.

  2. Draft and review the update

    Use the release note with your assistant to propose a focused edit. Check the steps against your product.

  3. Preview and publish

    Save the change as a draft, open the preview, and publish when the instructions are ready.

Try a docs update

Which product changes belong in the docs?

  • A screen or button moves

    Update the navigation path and screenshots in the how-to guide. Check linked onboarding articles for the old label.

  • A feature rolls out by plan

    Add plan and permission requirements to the feature guide. Keep the steps for users who still see the previous experience.

  • An API behavior changes

    Bring a pull request or changelog entry. Update the affected request example, error guidance, and any quickstart that uses the old behavior.

What to check in a release draft

  • Bring the old article, a short description of the change, and the date or rollout stage.
  • Confirm you can follow the new steps using an account with the same permissions as the reader.
  • Check screenshots, examples, and links in preview. Publish when the author and reviewer agree the change is ready.
DocsAlot visual editor with an example documentation page open
DocsAlot visual editor · example workspace

What teams say about their DocsAlot sites

"Fantastic stuff! The introduction perfectly nails the Mako Code's idea. I particularly enjoyed the Technical Deep Dive with its explained code snippets, and the Project Architecture's file tree was both cool and useful."
Hoyt Emersonsenior product manager · brillio
View their docs
"I don't know what you did, but it's amazing. Just having our docs on DocsAlot gave us an uptick in SEO, the page-load speed is super fast, and auto-sync is a game changer."
Jawad Alihead of engineering · masonhub
View their docs
Do updates publish automatically?

You can review a draft and decide when to publish. Start with the editor for a single change.

Do I have to move all my docs?

You can try one article in a separate DocsAlot workspace while your current site stays live.

What can I use as the source for an update?

Start with a release note, product ticket, or a short summary of a pull request. Include what changed, who is affected, and when the new steps apply.

What should I do if the release is staged?

Write the draft ahead of time, record who has access to the new behavior, and publish once those readers can follow the instructions.

Try it with your next release note.

Open the DocsAlot editor and start with one article.