Guide

Plugin System

Plugins extend PostSnail without becoming part of Core. Install does not mean load, enable does not mean load everywhere, and routes decide what assets load.

Plugin Manifest

Plugin manifests declare protocol postsnail-plugin-v1, id, name, version, requiredFeatures, optionalFeatures, extensions, capabilities, permissions, admin entries, export hooks, runtime assets, state versioning, and budgets.

Official Bundled Plugins

The admin Extensions tab can install, enable, and disable official plugin manifests shipped with PostSnail. postsnail-snaillift exposes deployment assistants, postsnail-pages exposes the Pages CMS tab, and postsnail-comments exposes signed comment moderation.

Plugin Registry

createPluginRegistry, installPlugin, enablePlugin, and disablePlugin are pure state helpers for official validated manifests. They do not execute plugin code.

Hook Planning

planPluginHooks returns deterministic structured plans for declared hooks. Alpha 2 does not dynamically import or run arbitrary plugin JavaScript.

Route Runtime

Public plugin runtime assets must use route-scoped runtime declarations through loadWhen. Plugins must not load globally by default.

Private State

Private plugin state remains inside the encrypted Shell. It may survive workspace migrations, but it must not be copied into the public Website ZIP.

Feature Gates

Unknown optional plugin features are ignored safely. Unknown required plugin features fail clearly.