The future of Strapi

We move on

If you were following us on Slack during the last few months, you probably noticed that new features and improvements have been implemented on Strapi on the v2 branch.

Before you continue to read: we opened an issue on GitHub to share with you our feelings about the v2. Please feel free to give us your opinion in this issue to help us making the right decisions:

Discuss about the future of Strapi here: https://github.com/wistityhq/strapi/issues/126

The observation

What we did

During the last few months, we tried to build an open-source solution to speed-up back-end development. Strapi was divided in two parts: the open-source part and the SaaS part (aka the Studio). We thought we would be able to monetize the SaaS part to continue developing the open-source part. We went wrong.

So, we stepped back and looked at how you were using Strapi. We analysed your behavior, what kind of project you built, what are the main features you used on a regular basis and we gathered a lof of feedback.

The conclusion

  • Using the Studio is too complicated. As a user, you have to create an account and login. Then, you have to copy the secret key inside your project and wait for the synchronization. Also, the Studio is a central part of Strapi and our community deserves great tools to grow. The SaaS hosting is a serious bottleneck for this tool.

Solution : We should host it on your own machine.

  • Having two interfaces (admin panel and Studio) is an opinionated choice we made at the beginning. As a user, you have to switch between them everytime. Most of you use the admin panel as a tool to help you to debug your project. This is also the Studio’s goal.

Solution : We should merge these two interfaces.

  • Adding new features on Strapi is too limited for now. As a user, you will be able to easily extend a project functionalities. This is called a plugin.

Solution : We should build a Strapi ecosystem around a set of plugins.

We are proud about what is Strapi now. We built a strong, lovely and dedicated community. You love the product, the feedback are amazing but we are convinced the product could be even more adapted to real use cases. That’s why we decided to move on...

The future of Strapi

Every features will be plugins

Plugins will be pieces of code having a single purpose: extend Strapi projects’ features. Every extra-feature will be a plugin. Here is a list of examples:

  • API Manager* : plugin used to visually create APIs (equivalent of the API Builder which is currently in the Stu\dio).
  • Configurator Manager* : plugin used to manage settings of the framework (equivalent of the Settings section of the current Studio).
  • Data Explorer* : plugin used to explore the data of your project (equivalent of the current admin panel generated inside each project).
  • Users & groups* : plugin used to add a complete user API with JWT authentication on your project (equivalent of the current users and groups feature of the current admin panel.
  • Deploy Manager* : plugin used to easily deploy on the future Strapi Cloud or even on your own servers.
  • Stripe : plugin used to easily integrate the Stripe payment solution in your project with a minimalist dashboard in your admin panel.
  • MailChimp : plugin used to easily send email to a single or a list of users.
  • And many more...

    *- These plugins will be installed by default in each generated Strapi application. Of course, they will be removable as well.

“All of these plugins will be available in a single marketplace.]“

A single marketplace

All of these plugins will be centralized in a single marketplace. So, as a developer, you will be able to easily share and sell your own plugins.

Even more powerful: as a service provider, you will have the possibility to offer plugins based on your own service, and monetize it thanks to a monthly payment (eg. a monitoring system).

We will highlight the best and most popular plugins on the marketplace to maintain a high quality service. These plugins will be reviewed by our team and they will have an “official” label.

Also, a few free plugins will be installed by default in every new Strapi project to offer the most basics needs (authentication, users & groups, data explorer, configurator).

A new admin panel

One place to do whatever you want. This admin panel will be open-source. It will be a kind of hub to connect plugins together. This means you will be able to find the same features as the current Studio and admin panel for free on your machine.

From four to three

As you may know, Loïc is leaving the project. We wish the best for him on his next project! The whole team want to thank you for what you did on the project and for us. This was an awesome adventure, we shared a lot during the three years. Keep on your hard work bro!

Community-driven

One of our goal is to be community-driven. You, as part of the Strapi community, give us feedback on a daily basis. This is incredibly helpful and inspiring for the project and our team. As much as you we will able to do it, we will follow your requirements and suggestions.

Be transparent, no bullshit

We want to be as transparent as possible. Strapi can become an amazing tool if we build it together. So, we will do our best to keep you informed on a regular basis.

“Strapi is intended to become the perfect balance between a CMS, a framework and an automation tool to speed-up back-end development and management.”

We need you!
To achieve this dream, we absolutely need you. More than ever_, your feedback is welcomed.

Please comment this issue related to this post: https://github.com/wistityhq/strapi/issues/126