> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcdemo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Write guides people can follow

> Make each instruction clear, useful, and connected to the result on screen.

The screen shows the interface; the guide explains what to do and why it matters. Write for someone who did not attend your planning meeting and may be viewing the demo on a smaller screen.

## Give each step a job

Use a short action followed by the reason when the reason is not obvious:

| Instead of | Try |
| - | - |
| “Here is the dashboard.” | “Select **Late** to focus on orders that need attention.” |
| “Click here to continue.” | “Open an order to see its owner and delivery status.” |
| “Our powerful reporting engine provides visibility.” | “See which orders need follow-up.” |

The examples describe a fictional product. Use the exact labels shown in your own capture. A reader should be able to find the target without guessing what “here” means.

## Match the instruction to the screen

1. Select the step and check the screen's actual state. The control you mention must be visible and readable.
2. Place the guide near its target without covering the information the viewer needs. Preview it at the sizes where the demo will be used.
3. Give the viewer one clear action. Put supporting context in a separate sentence rather than stacking several actions into one paragraph.
4. Check the next step. It should show the result promised by the instruction.
5. Read the whole flow aloud. Remove repeated introductions and unexplained product jargon.

A guide can introduce a transition or summarize a result; not every step needs to tell someone to click. If you use narration, retain the essential instruction in text so the demo works with sound off.

## Write an ending that fits the context

On a website, the next action might be “Start a trial.” In a support article, it may be “Return to your account and try this workflow.” A sales follow-up might invite a relevant conversation. Make the action specific and test its destination in the published demo.

If you offer choices, name the outcome of each choice. See [Build paths for different viewers](https://docs.arcdemo.io/guides/viewer-paths.md), then test each path with [the review checklist](https://docs.arcdemo.io/guides/review-and-publish.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.