Skip to content

Step-by-step guides

Every demo is also a written guide.

Publish a demo and AtriumKit writes it out as a help article, with one numbered step per click, a picture of the screen with the spot highlighted, and your branding. Share its link or paste it into the docs you already have.

  • Free (included)
  • Pro (included)
  • Team (included)

The guide page

A help article you didn’t have to write.

Each guide has its own page next to the demo, with your brand kit’s header, colors and fonts. Readers can follow it without clicking through anything, then open the interactive version when they want to try it.

  • Numbered steps with a picture each, and a contents rail when the guide has sections
  • Chapter cards become sections; the intro and closing cards open and end the guide
  • Branching paths read as “If you chose…”, with links to the right steps
  • Open the interactive demo takes readers to the demo itself
  • Access follows the demo, and one email at the gate opens both

Exports

Paste it into the docs you already have.

From the guide editor, copy the guide with its pictures, download it as Markdown, or print it. The highlight is drawn into each picture, so it still makes sense outside AtriumKit.

  • Copy → Rich text pastes into Notion, Google Docs and Confluence with the pictures
  • Copy → Markdown, or Download .md
  • Print / PDF opens your browser’s print dialog, with no step split across pages
  • Every hosted guide also has a Markdown version at its own link
  • Copy and Download use your latest draft; Print / PDF and the hosted guide show the published version

Guide copy

Write it as instructions, not a tour.

Tooltips in a demo often sell. Steps in a guide should tell people what to do. Give any step its own wording for the guide, or leave it out, and the demo keeps its own copy.

  • Title in the guide and Text in the guide replace a step’s copy in the guide only
  • Hide from guide leaves a step out
  • Write guide copy drafts plain instructions with AI, like “Click New invoice”, using AI credits
  • Guide wording is translated with the rest of the demo, and readers can switch language (translations are on Pro and Team)

Search and analytics

Ready for search. Measured when read.

A public guide is a real web page. It carries what search engines and link previews look for, and it reports how many people read it.

  • schema.org HowTo data, a canonical link and a social preview with the demo’s cover
  • Language alternates for every translation of a public guide
  • Unlisted and gated guides ask search engines not to index them
  • Readers on every plan; exports and how far readers got on Pro and Team
  • Reading a guide never counts as a demo view

How it works

  1. 01

    Publish the demo

    The guide goes live with it, on the same access settings.

  2. 02

    Tidy the wording

    Open Guide, rewrite a step for readers, hide one, or let AI draft the instructions.

  3. 03

    Share or paste

    Send the guide’s link, or copy it into your help center, wiki or doc.

Use cases

Teams that use it

FAQ

Questions, answered.

Do I have to do anything to get a guide?

No. Every published demo has one, on every plan. To turn it off, use the Step-by-step guide switch on Share or Guide page in the guide editor; its link then answers “not found” and the demo stays up.

Does the guide update when I change the demo?

The hosted guide updates every time you publish the demo. Anything you pasted elsewhere is a copy, so paste it again after big changes.

Do clickable demos get a guide too?

Yes. A clickable demo’s guide follows the path you recorded, one screen at a time.

Can I download a PDF?

Print / PDF opens the guide in your browser’s print dialog, where you can save it as a PDF. Pictures are sized for paper and each step stays on one page.

Where else do guides show up?

On Pro and Team, every live demo’s guide is an article in your internal knowledge base. AI assistants connected through MCP can read guides too.

Your next demo is one click-through away.