13 docs tagged with "plugins development"

A Strapi plugin can interact with both the back end and the front end of a Strapi application. The Admin Panel API is about the front end part, i.e. it allows a plugin to customize Strapi's admin panel.

The Content Manager APIs reference lists the APIs available to plugins for adding actions and options to the Content Manager List view and Edit view.

Generation introduction about Strapi plugins development

Learn how to migrate your Strapi plugins and applications to not use the `helper-plugin` package.

In Strapi 5, the `helper-plugin` is removed. A whole migration reference is available for plugin developers, and codemods will automatically handle some changes.

Learn how to store and access data from a Strapi plugin

In Strapi 5, the lockIcon property is replaced by licenseOnly, which affects how the addMenuLink(), addSettingsLink(), and addSettingsLinks() methods from the Admin Panel API work.

Learn how to use the Plugin SDK to build and publish a Strapi plugin

Reference documentation for Strapi's Plugin SDK commands

Learn more about the structure of a Strapi plugin

Strapi comes with plugins that can be installed from the Marketplace or as npm packages. You can also create your own plugins (see plugins development) or extend the existing ones.

The present page is intended to be used as a short summary of everything to consider if you are a plugin developer upgrading your plugin from Strapi v4 to Strapi 5. The page quickly describes the changes affecting plugins and links to additional resources where necessary.

Learn more about TypeScript usage with Strapi 5