> ## 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.

# Build and check a sandbox

> Review captured pages, connect them, and test the paths viewers can explore.

A sandbox connects captured page states so a viewer can explore an experience. Capture the screens and transitions that matter to the story, then review the journey in the editor. A captured page is a snapshot of the product at that moment; check it after the product changes.

## Plan the states, not just the screens

Suppose a fictional order dashboard has a list, a filtered list, and an order detail. The list and filtered list may look like the same page, but they show different results. Capture both if a viewer needs to see what the filter changes. Capture the detail state too, then connect the relevant controls.

| Starting state | Viewer action | Expected destination |
| - | - | - |
| All orders | Select **Late** | Filtered orders |
| Filtered orders | Open an order | Order detail |
| Order detail | Return to orders | An appropriate list state |

Adapt this table to your product before recording. Include the return path and any important alternative route. A sandbox is a collection of captured states and connections; it should not be assumed to run the original product's backend or support every action from the live application.

## Review the starting point

Open the sandbox in the editor, select **Flow**, then choose **Open journey map**. The map lists captured pages and links. Find the page a viewer should see first and choose **Set as start**. Rename pages when clearer names will help your team recognize them.

## Connect pages

For a page with an available HTML preview:

1. Select that page in the editor and choose **Add link** in the journey map.
2. Click the element on the page that should lead somewhere. Press Escape to cancel picking.
3. Choose the destination page and whether the link applies to this page, selected pages, or every captured match.
4. Review the affected pages in the preview before applying. When a link applies across pages, publishing checks that the selected element can be found on each selected page.

Use a narrow scope when controls only look similar. After adding a link, preview it from the source page and check the destination. Removing a link can affect multiple captured pages, so read the confirmation before deleting it.

## Resolve journey warnings

The map can flag a missing link target, multiple enabled links on the same element, possible duplicate pages, or pages not reachable through recorded links. A page marked unreachable may still be reachable through a page URL, so treat the warning as a prompt to test rather than proof that nobody can reach it.

Review each intended path, including the start page and any [audience routes or presenter path](https://docs.arcdemo.io/guides/viewer-paths.md). Test the published version after [publishing](https://docs.arcdemo.io/share/publish.md); later edits remain in the draft until you publish again.

## Test the experience as an explorer

Start at the entry point, take each intended route, and try returning to the main path. Test links that look alike across different states: a link scoped to every captured match may lead to an unexpected destination on one of them. If an action does nothing, check that its source element exists in the captured state and that the target page is included in the journey. Recapture or reconnect the relevant state when necessary.

After a product change, compare each affected state with the current interface. A correct starting screen does not prove the filtered or detail state is still accurate. See [Keep a demo current](https://docs.arcdemo.io/guides/maintain-a-demo.md).


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