Publishing
Publish your plugin
Bring a useful Omarchy extension to the community. You keep the code in your GitHub repository; the marketplace reads its manifest.json.
The marketplace never hosts your plugin.
Your repository remains the source of truth for code, releases, documentation, and licensing.
Prepare the repository #
Your plugin should work on a current Omarchy installation and provide enough context to evaluate it.
- ✓Public GitHub repositoryReachable over HTTPS without authentication.
- ✓Manifest in the repository rootA valid manifest describes the plugin.
- ✓README and licenseDocument purpose, usage, and licensing.
- +Optional repository previewAdd a
preview.pngto the repository root and the marketplace will display it automatically. - ✓Safe install and removalDo not overwrite user configuration without consent.
Add a manifest #
Keep the manifest in sync with every release.
Start with omarchy plugin clone, validate with omarchy plugin validate, and consult the official Omarchy Quattro plugin reference ↗.
JSON manifest.json
{
"schemaVersion": 1,
"id": "yourname.plugin",
"name": "Plugin name",
"version": "1.0.0",
"author": "Your name",
"description": "What the plugin does.",
"kinds": ["overlay"],
"entryPoints": {
"overlay": "Plugin.qml"
}
}FieldPurposeRequired
schemaVersionOmarchy manifest contract versionYesidUnique namespaced plugin identifierYesnameHuman-readable nameYesversionCurrent semantic versionYesauthorPlugin author shown in the marketplaceYesdescriptionShort marketplace summaryYeskindsPlugin capabilities exposed to OmarchyYesentryPointsQML entry file for each plugin kindYesOpen a submission #
Submit the repository URL, category, and useful tags through the GitHub issue form.
Review and publication #
A maintainer reviews function, documentation, safety, and marketplace fit. Approval adds one registry entry; GitHub then rebuilds the catalog automatically.
- 1ValidateManifest, URL, license, unique ID
- 2ReviewPurpose, quality, safety
- 3PublishRegistry merge and deployment