Plugins

Plugins add optional public output, administration, CLI commands, imports, exports, or scheduled work. First-party plugins are included in the release and are inactive unless the installation enables them or the release configuration says otherwise.

A superadmin enables plugins under System > Plugins. Plugin settings appear in the relevant system area, profile area, Composer, or plugin administration page. A plugin can expose different capabilities to the root site and author spaces.

Check a plugin's page before enabling it. Some plugins add public routes or shortcodes. Others require credentials, scheduled commands, or writable private storage. Plugins that fetch remote data for public display use saved cache data during visitor requests.

Before disabling or removing a plugin, check whether it owns public routes, shortcodes, scheduled jobs, stored files, or content lifecycle effects. Disabling code does not necessarily remove its stored data.

Static exports handle each public plugin according to its documented export mode. Some output is included directly; some remains available only on the live site.