Share a mockup

Turn a page, prototype, screenshot, or file into a real, shareable link — in seconds, with no deploy and nothing to set up.

Who this is for

You want to show someone something — a landing-page draft, a screenshot, a short demo video, a one-page proposal — before it's "real." You don't want to wait on a deploy, and you don't want to email a file back and forth. You just want a link you can drop in chat.

Before you start

• A bot — no setup, no admin approval, no toggle to flip. The first time you ask your bot to publish something, it just works.
• Something to share — a page your bot is designing, a file you already have, or something your bot builds fresh from your description.

Steps

1. Ask for a link. Describe what you want shared: "Publish this landing page draft so I can look at it on my phone." or "Turn this into a shareable page." Your bot puts it live and gives you the URL right away — no waiting, nothing to deploy.

2. Share it with anyone. The link works for anyone you send it to, no account needed on their end. Drop it in a message, an email, a Slack channel — whoever opens it just sees the page.

3. Choose who can open it, if the default isn't right. Every shared page starts out open to anyone with the link. If that's not what you want, tell your bot:

   • "Make that page password-protected" — your bot sets a password and hands it to you to share separately from the link (so someone can't open the page from the link alone).
   • "Hide that page — only I should be able to see it" — the link stops working for everyone except you.
   • "Make it public again" — back to anyone-with-the-link.

   A password-protected page shows any visitor a simple password prompt before the page loads; once they enter it correctly, they're in for several hours without being asked again.

4. Iterate freely. Keep describing changes — "make the headline bigger," "swap in the new logo," "try a dark background" — and each one lands on the same link. Nothing you had before is lost.

5. Roll back if a change doesn't land. "That last change made it worse — go back to the version before it." Your bot can restore any earlier version; restoring doesn't erase the versions in between, so you can always come back to try something else.

6. Let people leave feedback right on the page, if you want it. Every shared page can carry a small on-page comment tool — a visitor clicks a spot on the page and leaves a pinned note right there, instead of describing "the button near the top" in a separate message. Ask your bot to turn it on or off, and to tell you what mode you want:

   • Just let me know — comments come to you as things to review; your bot never acts on one automatically.
   • Anyone who knows a shared word can direct changes — set a comment password and share it with people you trust to make requests directly.
   • Hold every comment for me to approve — nothing happens until you say yes to each one.
   • Anyone with the link can direct changes — the loosest setting, useful for a small trusted group.

   You (or whoever you designate) can also mark comments resolved or delete ones that don't apply once they've been handled.

7. Check what's changed, if you want the history. "Show me the version history for that page" — a visitor (or you) can flip through earlier versions right on the page and compare two side by side, without you doing anything extra. Ask your bot to turn this off for a given page if you'd rather it stay clean of that control.

What you'll see

• In chat: the live link the moment it's published, a password if you asked for one, and a summary of what changed each time you update.
• On the page: your content, exactly as described — plus, if turned on, a small corner control for version history and comments. Nothing extra shows unless you asked for it.
• In the dashboard: every shared page for a bot, with its version count and any pending comments waiting for your attention.

When to graduate to a real deploy

A shared mockup is built for speed, not for a permanent home — it doesn't have your own domain, and it's meant to be replaced or outgrown once you've settled on a direction. Once you're happy with a design and want it on your own domain with a real deploy behind it, tell your bot to build it out properly. See Launch a landing page for going from a mockup to a live custom domain, or Build & deploy an app for something with more than a single page behind it.

Troubleshooting

• The link says the page isn't found. Double-check you're using the exact link your bot gave you — ask your bot to resend it. If you recently asked to hide the page, that's expected: only you can still open it.
• A visitor says the password prompt won't accept the password. Ask your bot for the current password — if it was changed since you last shared it, the old one no longer works.
• A change you asked for doesn't show up. Give it a few seconds and refresh — if it still isn't there, ask your bot to confirm the update actually landed, or try describing the change again more specifically.
• Comments aren't reaching your bot. Ask your bot what comment mode the page is set to — if it's set to hold comments for your approval, they're waiting for you to review, not lost.
• You shared a password-protected link and the recipient can't get past the prompt. Make sure you sent the password through a separate message from the link itself — that's the point of the password mode, so double check you actually sent it.

Going deeper

• Built-in tools — the concept page
• Launch a landing page — take a mockup to a real custom domain
• Build & deploy an app — when a shared page grows into a full app