Introduction to plugins
Strapi is built around different types of plugins. Every default Strapi application comes with the following pre-installed plugins:
- Content Manager (see Introduction to the Content Manager)
- Content Type Builder (see Introduction to the Content-type Builder)
- Media Library (implemented via the Upload plugin)
- Roles and Permissions
These plugins are essential for your Strapi application to function and cannot be uninstalled.
Additional plugins that you can use to extend and customize your Strapi applications are available in the Marketplace. This section focuses on how to install and manage these additional plugins.
From the admin panel, administrators are allowed to:
- discover additional plugins and providers in the Marketplace (see Managing Marketplace plugins)
- review the currently installed plugins and providers in Plugins
Some plugins can be further extended through the configuration of providers, packages designed to be used on top of an existing plugin and add a specific integration to it. For example, you can use the AWS S3 provider to extend the Media Library plugin and store files in your S3 bucket rather than locally on your server.
Currently, the only plugins designed to work with providers are the:
- Email plugin, and
- Media Library plugin (implemented via the Upload plugin).
Some plugins can add custom fields to Strapi. Custom fields are a way to extend Strapi’s capabilities by adding new types of fields to content-types or components.
Once added to Strapi (see Marketplace), custom fields can be created in the Content-type Builder and used in the Content Manager.