← Back to the developers overview
Developer documentation
The same material as in the developer cabinet — open without signing in.
- How it works — A package’s path: developer account, signing, submission, review, publication, payouts.
- Extension package — Directory layout, manifest, translations and building the ZIP with package_artifact.py.
- Extension manifest fields — code, version, platform, capabilities, entrypoints, settings_schema and the other required fields.
- Language pack — language-pack.json, translation catalogues and archive limits.
- Themes — Theme package format: theme.json, design tokens, screenshots, build and limits.
- Signing a package — Ed25519 key, SHA-256 checksum and what exactly is verified.
- Submitting a version — Form fields, limits and what happens after you send it.
- Checks and moderation — Automated archive checks, submission statuses and rejection reasons.
- Sales and payouts — The 70/30 split, daily payouts and dual approval.