Plugin Distribution

Plugins extend Syntic Code with capabilities specific to your organization: commands that follow your conventions, skills that encode your best practices, and tools wired to your internal systems. Building a good plugin is only half the job. The other half is getting it into your developers’ hands reliably and keeping it up to date, which is what this section is about.

From building to distributing

A plugin that lives on its author’s laptop helps one person. To help a team, it needs a distribution channel, a versioning story, and a way for developers to discover and adopt it. This section covers the mechanics of all three: publishing plugins through a marketplace, pinning the versions everyone runs, and the two paths for recommending a plugin, one from the CLI for a single developer and one from a central policy for an entire organization.

What each page covers

• Marketplace explains how to publish plugins to a catalog your developers can browse and install from.
• Dependency Versions covers pinning and updating plugin versions so a fleet stays consistent and upgrades are deliberate.
• Recommend from the CLI shows how one developer can suggest a plugin to teammates from within syntic.
• Recommend for an Organization describes how an administrator can push a recommended or required set of plugins to everyone.

Start with Marketplace to establish where plugins live, then use Dependency Versions to keep them stable. The two recommendation pages then cover the grassroots and top-down paths for driving adoption, which work best in combination.