Skip to content
Browse documentation
DocumentationPublishing & history
Your workspace

Publishing & history

Save a draft, publish a snapshot, and connect eligible hosted checkout.

Save the draft

“Save changes” persists your current project draft. The saved draft preview uses this saved state. It does not update an already published snapshot.

Opening a saved draft in another tab before saving will show the previous saved version.

Publish a storefront snapshot

Choose a valid project URL slug, then publish. If the editor offers “Save & publish,” it saves the current changes before publishing the snapshot.

Your published storefront appears at /s/your-project-slug. Later draft changes stay private to the draft until you publish again. Published-link access follows the site’s access settings.

Connect first. Publish explicitly.

Checkout requires a verified template purchase and Tebex merchant connection on a supported native storefront. A demo catalog, imported catalog snapshot, or custom HTML storefront never enables checkout.

Connect Tebex for hosted checkout

Hosted checkout supports Minecraft stores across all eight native design families. The project owner must connect the BuiltByBit account that purchased the selected template and verify access.

Complete the separate Tebex merchant connection using your store’s Game Server secret for one-time verification and its public Headless token. This verifies the merchant connection; importing a catalog alone does not complete this step.

Review your native storefront and explicitly publish it after verification. Connecting Tebex does not automatically publish your draft. Customers can then use the eligible published storefront to reach Tebex checkout; Tebex handles payments and package delivery.

Demo content, catalog imports, and custom HTML do not activate hosted checkout. CompactEditor project ZIPs are backups for the editor, not installable Tebex theme downloads.

Restore an earlier version

Open version history to see saved published versions. Restoring a version copies its supported state into your draft, where you can review and adjust it.

Restore does not automatically replace the published storefront. Publish again when you want the restored draft to become the next snapshot.