Preview and Publish Your Site
Preview your edits on the live canvas, review the diff for every changed file, then ship: open a pull request or commit and push through your own deploy pipeline.
Overview
Your edits run against a local dev server, so the canvas is already a live preview. Before you ship, you review what changed file by file. Then you publish: Studio commits your edits on a draft branch and either opens a pull request on your GitHub repo or commits and pushes directly. Your own deploy pipeline takes it to production.
1. Preview on the canvas
The canvas renders your running site, so your edits show up as you make them through hot reload. Use the viewport toggle (desktop, tablet, phone) to check the layout at each width, and the page switcher to move between pages. Switch the canvas to Interact mode to click through the site like a visitor before you ship.
📘 Media pending
Screenshot of the canvas preview at a narrow width hasn't been captured yet.
2. Review the changes
Open the Changes panel in the sidebar. It lists every file you've touched, with a status (added, modified, deleted, renamed) and the count of lines added and removed. Click a file to open its diff and read the exact before and after.
If the diff touches a value that's easy to get wrong, like a URL or a number, Studio flags it at the top of the diff and asks you to verify it. You can discard a single file's changes from the diff view if you don't want them.
📘 Media pending
Screenshot of the diff view hasn't been captured yet.
3. Ship it
Click Ship in the top bar to publish. Studio commits your edits on the draft branch and, for a connected GitHub repo, opens a pull request. The banner that appears links straight to the PR. For solo work, it commits and pushes directly instead. Your site deploys the way it already does, through your own pipeline off that branch or PR.
The publish banner tells you the outcome:
- Published. Your edits are committed. If a PR was opened, the banner links to it.
- Nothing to commit. There were no changes to ship.
- Failed. The publish didn't go through.
- Build failed. The project didn't build. The banner shows the build output and a Fix with chat button to hand the error to the agent.
📘 Media pending
Screenshot of the publish banner hasn't been captured yet.
4. Undo a publish
If you need to walk a publish back, the banner for a successful publish has a Revert button that undoes the commit on that branch. Use it when you shipped something you didn't mean to.
📘 Media pending
Screenshot of the revert control hasn't been captured yet.
📘 Good to know
Studio ships to your existing deploy pipeline through the branch or PR. It doesn't host your site or run the deploy for you. Production builds the committed branch the same way it builds any other commit.
Where to go next
- Edit a page visually to make more changes before you ship.
- Use the agent for hard edits when a build fails and you want help.
- Example: edit your pricing page for the full edit-to-publish loop.
- Website Studio for the overview.
- Desktop App Overview for the rest of the desktop app.
Use the Agent for Hard Edits
When a click can't make the change, hand it to the Studio agent chat. The agent resolves indirect values like translated strings, mapped lists, and prop-driven components across the files they touch.
Example: Edit Your Pricing Page
A worked example: edit a price on your pricing page, preview it, connect the site to Intempt's analytics, and publish the change through your own pipeline.