17 docs tagged with "plugins"

Overview of the Admin Panel API for Strapi plugins, with entry file, lifecycle hooks, and available actions for customizing the admin panel UI.

Configure Strapi Cloud to use a third-party email provider.

By using Swagger UI, the API documentation plugin takes out most of your pain to generate your documentation.

Find some answers and solutions to most common issues that you may experience when working with Strapi.

Use a GraphQL endpoint in your Strapi project to fetch and mutate your content.

Learn how to create and configure admin permissions for your plugin

Learn how to create and configure components for your Strapi plugins

Learn how to pass data from server to admin panel with a Strapi plugin

Learn how to store and access data from a Strapi plugin

The in-app Marketplace lists plugins and providers with badges, search, and “More” links to detailed Strapi Market pages. This documentation outlines browsing cards and following provider-specific instructions to install new integrations.

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 plugins have a single entry point file to define their configurations.

Existing plugins can be overriden by placing code in /src/extensions or using global register/bootstrap hooks. Instructions in this documentation cover reshaping plugin content-type schemas or server logic — altough upstream updates may break extensions.

Plugin developers upgrading from Strapi v4 to Strapi 5 must migrate to the Plugin SDK, transition from the Entity Service API to the Document Service API, update front-end code to use Design System v2 and remove helper-plugin dependencies.

Configure Strapi Cloud upload provider or use a third-party upload provider.