June 3, 2016
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
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.
Solution : We should host it on your own machine.
Solution : We should merge these two interfaces.
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...
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:
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.“
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).
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.
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!
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.
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