Saving and publishing
The four saved states, drafts, releases, visibility, versions and the product listing.
Four states#
| State | Where | Notes |
|---|---|---|
| Browser recovery | This tab | Automatic. Not a save. |
| Device save | This browser | Cmd/Ctrl+S. Survives restarts on this device only. |
| Account draft | Your account | Editable, private. Saving a draft never publishes it. |
| Release | The server | Immutable. Public, unlisted or private. |
Publishing#
Publish has four steps: choose access (public, unlisted or private, with license and fork permissions visible), review, let the server validate and create the release, and then see the playable and pinned links. Only a successful server response shows success.
Changing the access of an existing release has its own review step. It never publishes your current edits and never deletes copies people already downloaded.
Versions and changelogs#
A product has versions with semantic version numbers. Each new version must sort above the highest published one, and a changelog is required. Aliases such as stable and beta point at versions. A yanked version keeps its number reserved.
Listings#
A product page is generated from the release: title, description, preview and Frame image. You can override individual fields, add a gallery, manuals and FAQs as documents, and choose which fields come from the release. Creator documents appear at docs.tune.toys/@handle/<product>/docs/<slug>, rendered by the Tune.Toys server so changes and takedowns apply immediately. See Marketplace: selling.