Strapi is the leading open-source headless CMS used by millions of people all over the world. The needs of the community are becoming more diverse and complex. To unleash this potential we want to create and support a strong plugin ecosystem.
Build any plugin thanks to the redefined Plugin API coming with the v4. Easily design the plugin interface using the Strapi Design System and UI kit.
Strapi Market is the official and trusted place where people can access all the submitted plugins. Anyone is free to add their plugin to the marketplace. Our team will review the plugins and highlight the verified ones to give them maximum visibility. This is a foundational step to empower developers to get paid for their contributions in the future.
Finding the right balance between openness and trust is not an easy task. We aim to reach for the middle with an open and free marketplace and quality control to provide the best tools and security to Strapi users.
You can expect the first review of your plugin within 7 business days. You'll receive a notification when your plugin is live on Strapi Market. We'll let you know as well if you need to make some changes.
Strapi strongly encourages plugins developed by the community. All plugins will undergo a review process and will only be approved if all of the rules are followed. Please review these rules before beginning development to ensure your plugin is approved and published on Strapi Market as quickly as possible.
1. Make your code accessible through npm
Your plugin has to be hosted in a public npm registry.
2. Give your plugin a clear and representative name
Please avoid naming your projects anything that implies Strapi's endorsement. This also applies to domain names.
3. Add a logo or image
Add a representative image or logo, to make your plugin easily identifiable.
The image must be in JPG and be 160px x 160px.
4. Add an icon
The icon you will choose will help the users identify your plugin in Strapi's administration panel.
5. Provide a short and clear description
Briefly explain what your plugin does, and how it can help others in the community.
Your description must contain between 50 and 150 characters.
Please use capital letters sparingly.
6. Choose the MIT license
Please make sure your plugin is under MIT License.
7. Agree to the Terms & Conditions
You must agree to Strapi Terms & Conditions to submit your plugin.
strapias a peerDependency in their
@strapi/strapias a peerDependency in their
yarn auditto check for vulnerabilities.
The different screens in Strapi a plugin could be displayed on.
Plugins managing content for end-users should add collection and single types to the Content Manager. Clues will remind the users that these content-types are coming from a plugin. A screen can either be similar to regular content-types (ex: Mux) or custom (ex: Navigation Builder).
To display additional information or allow specific actions in the Content Manager, a plugin should use injection zones to embed simple components, such as a card with texts, or a button.
As part of the v4 release, many improvements will follow up shortly. Some of them are the way the plugins integrate with the different navigations. Here are the planned changes:
Note: Buffet.js is deprecated in v4.