How marketplace listings work
Where Orbit plugin listings live, how they reach the public catalog, and what authors submit in a pull request.
The registry and the catalog
Plugin listings are not stored in the Orbit framework repository. Authors open a pull request against the orbit-plugins registry with YAML, a thumbnail, and optional screenshots. After merge, the Orbit docs site clones that registry at build time and publishes the card on orbit.almasix.com/plugins.
What you submit
- An author profile (
authors/<slug>.yaml) the first time you publish. - A plugin listing (
plugins/<slug>.yaml) with summary, markdown description, categories, Orbit versions, and price. - Images under
public/plugins/<slug>/, referenced as site-absolute paths such as/plugins/<slug>/thumbnail.png.
Keep the thumbnail cropped to the feature (16:9). A full panel shot with sidebar and topbar reads as noise at card size.
After merge
Registry CI validates YAML and images. Merging to main rebuilds a small preview
site for reviewers and asks the Orbit docs workflow to rebuild, so the public
catalog updates without a separate Orbit commit.
Ready to list a package? Follow Get listed.
Figures
Related plugins
Orbit Branding
FreeSample panel plugin that sets a favicon and injects a boot-time render hook.
Orbit Permission
FreeOpinionated Users, Roles, and Permissions UI for Orbit panels, built on almasix-permission.
