Building panel extensions
Build a hosting control-panel extension for Salieno Core — the driver contract, the manifest, connection and credentials, testing, security, and publishing to the marketplace.
The mental model for panel extensions: a code-only driver that teaches Core to talk to a control panel, lit up by the capabilities you declare and delivered through the signed marketplace.
A hands-on walkthrough that builds a minimal but real panel extension end to end — the two-file package, the driver, its capabilities, a working create() and loginServer(), and how it reaches an install.
A complete field-by-field reference for salieno.json — the manifest that names your panel, wires its Server form, and sets the credential rules Core generates accounts from.
The definitive method-by-method reference for a panel driver: every signature, argument, and exact return shape Core reads, plus the objects and helper trait you build on.
How a panel's declared capabilities drive every Core screen — the full PanelCapability vocabulary, the control each one lights up, and why an honest subset makes a partial panel first-class rather than broken.
How a panel declares its Server connection form and account-credential rules in the manifest, and the helper trait every driver uses to make TLS-aware, well-masked API calls.
Prove your driver returns the exact contract shapes — with a syntax check, a faked-HTTP harness, and a static-scanner pass — before you submit it to the marketplace.
The full marketplace lifecycle for a panel extension — submit, review, signing on approval, pricing, the operator install flow, and shipping updates as an in-place atomic swap that loses no data and never re-charges buyers.
How the three gates — registered, genuine, entitled — let Salieno Core run third-party panel code safely, and what that means when you write yours.