miton
Request beta access

One-click publish

Package a Canvas project as a static site under a validated *.apps.miton.dev-style subdomain name.

Product stage
Development build
Last reviewed
2026-08-27
Successful result
The change is visible in the active project.

What this accomplishes

Publish builds your Canvas project into a static site and validates a subdomain name for it, shaped like <name>.apps.miton.dev. The design tokens the publish respects are in design tokens.

Current availability

This page documents behaviour verified in Miton development builds. Miton is still pre-release and is not publicly downloadable; invited beta users will receive a signed desktop build with automatic updates. Publishing today writes the built site to a local directory on your machine and returns its intended https://<name>.apps.miton.dev URL — it does not yet put that site on the public internet. There is no live CDN, DNS, or TLS certificate behind it at this stage.

Before you start

  • A Miton development build, an active project and Canvas open.
  • A connected model and permission to write project files when the task changes the app.

The subdomain name

Pick a name; it’s checked against the same rules a real *.apps.miton.dev subdomain would need: 4–63 characters, alphanumeric and hyphens only, no leading/trailing hyphen, no consecutive hyphens. “Available” today means no local build already exists under that name — it isn’t checked against a live public registry.

The publish flow

Publish packages the project’s current pages, tokens, and assets into a static build (HTML plus supporting assets) and writes it locally, keyed to the subdomain name you chose. Publishing again under the same name overwrites that build — there’s no version history, no rollback, and no side-by-side version comparison today.

What the publish flow does not cover

  • A live public deployment — see Current availability above. Nothing is served to the internet yet.
  • Version history and rollback — publishing overwrites the previous build for that subdomain name; there’s no way to keep or restore an earlier one.
  • An SEO meta editor — the generated page carries a <title>, viewport, and theme-colour meta tag. There’s no per-page meta description, Open Graph or Twitter card editor, canonical URL field, or generated sitemap/robots.txt.
  • Custom backend logic — the output is a static site; server-side logic goes through Code or an Automation webhook instead.

What success looks like

You can validate a subdomain name and produce a static build of the current project state on your machine, ready for whatever hosting path ships next.

Common failures and recovery

  • Confirm Canvas is editing the intended project and page.
  • Check the selected breakpoint, project permissions and model connection.
  • Reopen the last known-good project state before applying the change again.

Return to the Canvas overview to choose the next part of the project.