Did you already struggle with the assets management in Strapi? Like many users, you might have been experienced this particular pain point. Upload and upload again the same exact file. The reason was simple, Strapi didn't have a proper Media Library yet. Until now!
If you want to get more details about the Media Library, our fellow teammates Virginie and Alexandre will introduce you to how we designed, developed, and shipped this new feature. Hosted by Victor, you can register for the webinar below.
We are thrilled to welcome Kevin as our lead designer! He will give a fresh look to Strapi in the coming months both of the brand and product sides. He's here with his Buddy Victor 👉👈
Even, if we live through difficult times, we are very lucky to be in good shape and be able to hire new talents to join the team. If you want to be part of the journey, send us through your application!.
Having a stable version and leave the ßeta tag is our main priority. Most of the issues and enhancements to make are backend-related. We estimated the release date in May. We know that the word "stable" has different meanings according to your job position.
Our current definition is to ensure Strapi is stable from a new user perspective. From the installation to the development and deployment, the users must not encounter any major issues. That's why the stable will include the following fixes and improvements:
Then, to simplify the development of the next features we plan to release a new major version with a complete rework of our data management. It will include native support of the pagination and metadata through the API. New APIs to easily integrate plugins between each other will be introduced. More info will come in the next months. As it will include breaking changes nothing has been set yet. We would love to hear your insights before starting to develop it.
Last but not least, our second priority is the release of the permissions system, also called Role-Based Access Control. Our implementation will be a policy-based system. In other words, as a developer, you will be able to develop custom policy (functions) to restrict, or not, the access to resources. By default, Strapi will provide two policies:
The Users, Roles & Permissions is also the first feature that won't have unlimited access. Nevertheless, the good news is that even the enterprise edition of Strapi will be open-source. Only the license of the Enterprise Edition files will be different. Letting everyone contribute to the entire codebase is our main goal. We deeply investigated what was the best strategy, and we found that the Elastic Search and GitLab approaches were the best. Open-sourcing every single file.
The CE (Community Edition) will include the following functionalities:
The EE (Enterprise Edition) will unlock the CE limitations:
Making an open-source project sustainable without compromising its usage is one of the hardest challenges we have to tackle as maintainers. We are still looking for feedback to make sure we head in the right direction.
Feel free to engage with us and ask any questions you have by posting a comment below. We look forward to answering you!
See you soon 👋
Co-founder & Chief Product Officer, I started developing since I was 13 years old, I already developed 2 CMS before and am currently in charge of the product vision & strategy.