Marketplace

What this accomplishes

Browse and install themes, templates, and components from the marketplace.

The marketplace is the shared registry of themes, templates, sub-agents, and components in Miton’s Canvas. The marketplace is moderated; the marketplace is per-user; the marketplace is opt-in. The marketplace is the right shape for the user to extend the Canvas with community-contributed content.

This page is the marketplace. The blog post on the marketplace is at the Canvas overview (marketplace is the internal name; the public surface uses “marketplace” per ADR-0032). The sub-agent system (which the marketplace can host) is in sub-agents.

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.

What the marketplace hosts

The marketplace hosts four kinds of content:

• Themes — palette + font set combinations the user can apply to a project. The theme is a token set; the theme applies the token set to the project’s design.
• Templates — pre-built maker projects the user can fork. The template is a starter project; the fork creates a new project based on the template.
• Sub-agents — the sub-agents the user can install into the sub-agent registry. The sub-agent is a YAML file; the install creates a sub-agent in the user’s registry.
• Components — the custom components the user can add to the component library. The component is a YAML file; the install creates a component in the user’s library.

The marketplace is moderated. A submission to the marketplace is reviewed by a moderator before the submission is published. The moderation queue is in Settings under “Marketplace → Moderation queue”.

The submit flow

The user submits a theme, template, sub-agent, or component to the marketplace. The submit flow is:

1. The user creates the content in the user’s project.
2. The user opens the marketplace surface and clicks “Submit”.
3. The user fills in the submission form: the title, the description, the category, the tags, the icon.
4. The user attaches the content (the theme’s token set, the template’s project, the sub-agent’s YAML, the component’s YAML).
5. The user clicks “Submit”.
6. The submission is added to the moderation queue.
7. A moderator reviews the submission. The moderator can approve, reject, or request changes.
8. If the submission is approved, the submission is published to the marketplace. The user is notified.

The submit flow is per-user. The user can have multiple submissions in the moderation queue; the user can also withdraw a submission before the moderator reviews it.

The moderation queue

The moderation queue is a list of pending submissions. The moderator can:

• Approve — the submission is published to the marketplace. The submitter is notified.
• Reject — the submission is rejected. The submitter is notified with the reason.
• Request changes — the submission is sent back to the submitter with a list of changes the moderator wants. The submitter can revise the submission and resubmit.

The moderation queue is per-instance. A self-hosted instance has its own moderation queue. A user who submits to a self-hosted instance is moderated by the instance operator, not by the upstream maintainers.

The moderation queue is observable. The submitter can see the submission’s status (pending, under review, approved, rejected, changes requested). The submitter can also see the moderator’s comments.

The install flow

The user installs a theme, template, sub-agent, or component from the marketplace. The install flow is:

1. The user browses the marketplace.
2. The user picks a content item.
3. The user clicks “Install”.
4. The install runs:
   • Theme — the token set is added to the project’s token list; the user can apply the token set to the project.
   • Template — the template is copied to the user’s project; the user can fork the template.
   • Sub-agent — the sub-agent’s YAML is added to the user’s sub-agent registry; the sub-agent is available from the slash menu.
   • Component — the component’s YAML is added to the user’s component library; the component is available from the canvas builder.
5. The install completes; the user is notified.

The install is per workspace. A user who installs a theme in one project does not have the theme in another project. The user can configure the install to be shared across projects.

The per-workspace configuration

The marketplace is per workspace. The user can configure:

• Enabled marketplace — the marketplace to install from. The user can install from the official marketplace, from a self-hosted marketplace, or from both.
• Self-moderation — whether the user is the moderator of their own submissions. The default is the upstream moderator.
• Cross-workspace install — whether the install is shared across projects. The default is per workspace.
• Submission visibility — whether the user’s submissions are visible to other users. The default is public.

The configuration is per workspace. The user can change the configuration at any time; the change applies to the next install.

What the marketplace does not cover

The marketplace does not cover:

• Monetisation — the marketplace does not support paid themes, templates, or components. A user who wants to monetise their submissions can use a third-party platform (e.g. Gumroad, Patreon).
• Versioning — the marketplace does not support multiple versions of a content item. The submitter can update a content item, but the user cannot have multiple versions of the same item.
• Reviews and ratings — the marketplace does not support user reviews and ratings. A user who wants to evaluate a content item can read the description and try the item.

The marketplace focuses on the common case (a moderated registry of free content). The less common cases are covered by the user’s existing tools.

What success looks like

The marketplace is the right shape for the user to extend the Canvas with community-contributed content. The user can install themes, templates, sub-agents, and components.

The submit flow is the right shape for the user to contribute to the marketplace. The submission is reviewed by a moderator before the submission is published.

The moderation queue is the right shape for the moderator to review submissions. The moderator can approve, reject, or request changes.

The install flow is the right shape for the user to install content from the marketplace. The install runs in the background; the user is notified when the install completes.

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.