◈ UlanziDeck Store

Publish a plugin

Point to the repository and that’s it — the store reads the name, icon, languages and version from your manifest.json. Every new release becomes an automatic update.

  1. 1

    Have the plugin in Ulanzi’s format

    Structure from the official SDK — a folder ending in .ulanziPlugin:

    com.you.myplugin.ulanziPlugin/
├─ manifest.json        # name, version, icon, actions
├─ resources/icon.png   # plugin icon (square PNG)
├─ en.json  pt_BR.json  # languages (optional)
└─ plugin/app.js        # your code
  2. 2

    Publish a Release on GitHub

    The asset must be the zipped folder, with the same name:

    Release v1.0.0
└─ com.you.myplugin.ulanziPlugin.zip   ✅

    💡 The store template ships a GitHub Action that zips and creates the release on every git tag.

  3. 3

    Make the storefront shine optional

    A store.json at the repo root adds a cover and screenshots. Without it, the store uses the manifest description.

    {
  "cover": "resources/cover.png",
  "screenshots": ["resources/shot1.png", "resources/shot2.png"],
  "longDescription": "What your plugin does, in a line or two.",
  "deviceTypes": ["deck", "dial"],
  "tags": ["productivity"]
}

    Cover in 16:9 (e.g. 1600×900). Paths are relative to the repo root.

  4. 4

    Open a PR on the registry

    Create one file with just your repo and open the Pull Request:

    registry/plugins/you__myplugin.json
{ "repo": "you/myplugin" }

    File name = owner__repo.json (replace / with __). Once merged, your plugin shows up in the store. ✨

Open the registry on GitHub

Want to test before submitting? Turn on developer mode in the Helper and install straight from your repo.