Test the project as a visitor, create a shareable staging snapshot when needed, and keep preview, staging, and production publishing distinct so a review link never silently becomes a live release.
Where: Editor → Preview / Share — Click Preview to generate a staging link
Key ideas
- Visitor behavior: Preview removes editor selection interception so links, interactions, responsive layout, playback, and content can be tested as delivered.
- Staging snapshot: Share/Preview can export the current project to a sites.fmo.app URL that viewers can open without editor access.
- Not production: Previewing or staging does not promote the project to a custom production domain.
Steps
- Save the current project and select the page, composition, or state to review.
- Enter Preview/Interact and test navigation, hover/click/focus behavior, forms, scrolling, media playback, and reduced-motion behavior.
- Check representative phone, tablet, laptop, and wide widths rather than only the editor width.
- Use Share/Preview when collaborators need a URL and wait for the staging export to finish.
- Open the returned URL in a fresh session and verify its assets, metadata, links, and access behavior.
- Return to editing, correct issues, and create a new preview when the shared snapshot must reflect the changes.
- Use the separate production publish action only after final approval.
Preview versus staging
- In-editor Preview tests the active document.
- A staging URL is a hosted exported snapshot.
- Production publishing targets the configured live destination.
- Free projects without a custom domain may show a Made with Flowmo mark.
Tips
- Test once while signed out.
- Share the staging URL, not an editor-internal route.
Limitations and important notes
- A staging snapshot does not update merely because the editor changed.
- Preview is not a substitute for accessibility, SEO, or production-domain checks.
Troubleshooting
The shared page is stale.
Create a fresh staging preview after saving and confirm you opened the newly returned URL.