One-click publish

What this accomplishes

Publish your app to a free *.miton.app subdomain with versioning and rollback.

The publish flow is the one-click deploy of a no-code app or website to a public URL. The flow gives the user a free *.miton.app subdomain, the version history, the rollback, and the SEO meta editor.

This page is the publish flow. The blog post on publishing is at one-click publish with rollback; the design tokens (which 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.

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 free subdomain

The free subdomain is on *.miton.app. The user picks a name; the system checks availability; the system reserves the name. The published app is available at <name>.miton.app immediately after the publish completes.

The free subdomain is a real subdomain with a real TLS certificate (Let’s Encrypt, auto- renewed). The published app is served over HTTPS. The user does not have to configure anything.

The free subdomain is a Miton-operated service. The service runs the published app’s static assets; the service does not run the Canvas. The service is a CDN-fronted static host.

The free subdomain is subject to the Miton acceptable use policy. The user cannot publish content that violates the policy. The user cannot use the subdomain for phishing, malware distribution, or other abusive purposes. Miton reserves the right to suspend a subdomain that violates the policy.

The publish flow

The user clicks “Publish” in the maker toolbar. The publish dialog opens. The dialog shows:

• The current state of the app — the pages, the components, the data block schemas, the form schemas.
• The publish notes — a free-text field for the user to describe what changed in this version.

The user clicks “Publish” in the dialog. The publish runs in the background. The user sees a progress indicator. The user can keep working while the publish runs. The publish typically completes in under 30 seconds for a small app, under 2 minutes for a medium app, under 5 minutes for a large app.

When the publish completes, the user sees a notification with the new version number and a link to the published app. The user can click the link to open the published app in a new tab.

The publish is a snapshot, not a live binding. The published app is a static snapshot of the maker surface at publish time. If the user changes the Canvas, the published app is unchanged. The user has to republish to update the published app.

The version history

Every publish is a new version. The version number is v1, v2, v3, … and increments with each publish. The version number is visible in the versions list and in the published URL (<name>.miton.app?v=42).

The version contains the full snapshot of the Canvas at publish time. The snapshot includes the pages, the components, the design tokens, the data block schemas, the form schemas, and the static assets.

The versions are preserved for the lifetime of the project. The user can roll back to any version. The user can also compare two versions side by side.

The user can tag a version. A tag is a free-text label the user can apply to a version. The tag is visible in the versions list and in the version URL.

The rollback

The user clicks “Rollback” on a version in the versions list. The rollback dialog opens. The dialog shows the target version, the current version, and a warning that the rollback will replace the current version with the target version.

The user clicks “Rollback” in the dialog. The rollback runs in the background. The rollback typically completes in under 30 seconds. When the rollback completes, the user sees a notification with the new version number (the rollback itself counts as a new version) and a link to the rolled-back app.

The rollback is reversible. The rolled-back state is itself a version, and the user can roll forward to any version.

The rollback does not affect the Canvas. The Canvas continues to have the user’s latest edits.

The SEO meta editor

The user can configure the SEO meta for the published app. The SEO meta is per page; the user can override the default meta for any page. The SEO meta includes:

• Page title — the page’s title (the title shown in the browser tab and in the search engine results).
• Meta description — the page’s description (the description shown in the search engine results).
• Open Graph tags — the image, the title, the description (the metadata shown when the page is shared on social media).
• Twitter card tags — the image, the title, the description (the metadata shown when the page is shared on Twitter).
• Canonical URL — the canonical URL for the page (used by search engines to deduplicate content).
• Robots directives — the indexing and crawling directives (e.g. noindex, nofollow).

The user can also configure the sitemap and the robots.txt. The sitemap is auto- generated from the pages; the robots.txt is auto-generated from the user’s directives.

What the publish flow does not cover

The publish flow does not cover:

• Custom backend logic — the published app is a static app. The user cannot add custom backend logic. The user can use a workflow with a webhook receiver for backend logic.
• Real-time analytics — the analytics are aggregated; the analytics are not real-time. The user can use a third-party analytics service for real-time analytics.

The publish flow focuses on the common case (a static app on a free subdomain). The less common cases are covered by the user’s existing tools.

What success looks like

The publish flow is the right shape for the user to ship a no-code app or website. The user clicks “Publish”; the user gets a free subdomain; the user shares the URL.

The free subdomain is a real subdomain with a real TLS certificate. The user does not have to configure anything.

The SEO meta editor is the right shape for the user to optimise the published app for search engines and social media.

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.

Related next action

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