Publish
Shipping a Jx site is part of the Studio flow — no terminal, no separate deploy tool. The one boundary worth knowing up front: Studio publishes your code — it doesn't build or deploy the site. Studio's job ends when your files reach your repository; your host takes it from there.
How it goes live
In the Source Control panel, you write a message and Commit and sync — Studio records the change and pushes it to your repository.
The push wakes your host (or CI), which builds the project into plain HTML, CSS, and a little JavaScript.
The host serves that output from a CDN. Your site is live.
The deployment adapter you picked when creating the project — Static, Cloudflare Pages, Node, or Bun, with Cloudflare Workers also on offer in Project settings — tells the build how to package the output for your target. Switching hosts means switching the adapter; your pages, components, and content stay the same.
Every page is built ahead of time, so what the CDN serves is finished HTML however the site is put together. Pick one of the non-Static adapters and the same build writes a small worker beside those files for your host to run — that is what answers the
/_jx/*
routes behind a database, sign-ins, or server functions. A database or sign-ins make an adapter mandatory: the build stops with an error on
Static
. Server functions still build there, but nothing serves them without an adapter.
Build output and adapters
lists what each adapter emits.
Because every Jx file is plain JSON or Markdown, each publish is a clean, reviewable set of changes — no binary blobs, no database dumps.
The two surfaces
Source control — the built-in git client: review and stage changes, commit and sync, branches, pulling, and history.
GitHub — connect your GitHub account and publish a brand-new project as a repository in one flow.
Next
Understand the build and routing in Site architecture
Suite