Strapi email@example.com has been released, with many new features and improvements. Let's discover what's new!
What’s new in alpha.9?
Alpha.8 was mostly dedicated to fixing bugs. But don't worry, alpha.9 just landed to bring you awesome new features:
🚀 Authentication with providers
Authenticating your users with email and password combination is great. However, letting them subscribe to your API using their Facebook, Google, GitHub or Twitter account is even better. This is called Authentication with Providers, and now available with Strapi alpha.9!
The Users & Permissions plugin uses emails for some functionalities, such as Reset Password and Account Activation. Because your app deserves to be customised and potentially use another language than english, we gave you the ability to change the email templates content directly from the admin panel.
🚀 New configurations to disable sign-up and unique email
We gave you the ability to authorize, or not, registering multiple user accounts with the same email address (but connecting through different providers) and to enable/disable signup, within one-click.
Each permission rules was stored in the project's file. However, sometimes you need to update them in production, which was not possible with an horizontal scaling servers architecture since files were written on each server.
From now, every permissions rules are stored in the database instead of hardcoded files.
🚀 Analytics Plugin
Every company needs to know how its API is used: how many users did subscribe during the last two weeks? How many times the products list has been requested? How many users posted a comment between the 1st and the 15th of January?
That's why we are pleased to introduce you the new Analytics plugin. You will see it installed by default in the project generated by firstname.lastname@example.org. To get more informations, please schedule a demo.
Three winners will be drawn among people having retweeted our latest tweet before the February 14th 12:00am Paris time.
Strapi alpha.10 will be mostly dedicated to foundations consolidation. Every settings are currently stored in the projects files. Like for the permissions, you may need to update them in production. That's why we are going to store some of them in the database. Also, the input component that we are currently using in the admin panel start becoming a mess: before to go any further, we are going to make it easier to use.