26 docs tagged with "plugins"

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.

Learn more about Strapi 5 advanced features

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.

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

Send email from your server or externals providers.

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

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 pass data from server to admin panel with a Strapi plugin

Learn how to store and access data from a Strapi plugin

The Marketplace is where users can find additional plugins to customize Strapi applications, and additional providers to extend plugins. The Marketplace is located in the admin panel, indicated by Marketplace. In the Marketplace, users can browse or search for plugins and providers, link to detailed descriptions for each, and submit new plugins and providers.

The Internationalization feature allows to manage content in different languages, called "locales". Once the Internationalization plugin is installed in a Strapi application (see Installing plugins via the Marketplace), administrators can manage locales from Settings > Global settings > Internationalization.

Strapi is built around different types of plugins. Every default Strapi application comes with the following pre-installed plugins:

The Media Library displays all assets uploaded in the Strapi application. The Media Library settings allow controlling the format, file size, and orientation of uploaded assets. Those settings can be configured from Settings > Global settings > Media Library.

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 built-in plugins (GraphQL, Users & Permissions, Upload, API documentation, and Email) and you can install plugins as npm packages.

Strapi plugins have a single entry point file to define their configurations.

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.

Strapi builds and maintains plugins that extend the functionality of a core Strapi application. This section is a reference guide to the pre-installed plugins and additional plugins developed by Strapi, which are available in the Marketplace. Additional documentation on plugins is provided in the relevant sections of the User Guide and the Developer Documentation, however, a brief plugin description, how the installed plugin works, and changes to the admin panel is provided.

Upload any kind of file on your server or external providers.

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

Protect your API with a full authentication process based on JWT and manage the permissions between the groups of users.

Learn more about Strapi built-in plugins and how to use them from a developer perspective.