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.
Strapi strongly encourages projects developed by the community. All plugins will undergo a review process and will appear on the Marketplace. When and only when, all of the steps are approved, the submission will be displayed with an extra “verified” badge that will give it maximum visibility.
Please review these rules before beginning development to ensure your submission is approved and published on Strapi Market as quickly as possible:
The Strapi team will review the submission as soon as possible. The first review can be expected within 7 business days. Every notification will be sent via the provided email and Strapi will keep you updated if any changes are required.
Strapi users must feel confident when installing anything coming from Strapi Market. Strapi will not allow any submissions that are aimed to be malicious or damaging to the users or their work.
Please make sure to comply with the following rules:
npm audit
or yarn audit
to check for vulnerabilities.These are the prerequisites for your plugin or provider to be accepted on Strapi Market.
Each item can be modified afterward by sending an email to market@strapi.io with the requested changes.
Strapi created a whole Design System to help craft your own projects while providing a seamless experience for the users.
The project should follow the minimum standards given by the Design System, in terms of user experience and interface, in order to be approved. All necessary guidelines are available on the Design System website and the component library (see “Docs” tab).
Note: Buffet.js is a deprecated library used for v3 and which no longer exists in v4.
Strapi highly values clarity and consistency. The submission should fit in the whole Strapi experience.
By default, every plugin has a settings page. The project configuration should be done as much as possible through the UI to make it more accessible for anyone.
When it comes to meeting the community’s needs, Strapi could be really customizable. Additional information, fields, buttons, and so on, could be added to specific parts of the product thanks to “injection zones” (IZ). More are to be added, but we can currently count:
Thanks to the redefined Plugin API brought by Strapi v4, anyone is free to submit their idea(s) and project(s) to the Strapi marketplace.
strapi
as a peerDependency in their package.json
@strapi/strapi
as a peerDependency in their package.json
npm audit
or yarn audit
to check for vulnerabilities.