Simply copy and paste the following command line in your terminal to create your first Strapi project.
npx create-strapi-app
my-project
This month, we’re excited to announce the release of Strapi 3.5 with the Sentry plugin, the Single-Sign-On Authentication feature, and a bunch of improvements. More details in the post!
Everyone loves plugins: they help you connect your favorite tools, extend your software capabilities while keeping its core light and clean. In short, plugins help us build apps in a better, simpler, and more efficient way!
We at Strapi are not an exception. This year, we're planning to release more plugins and we are starting to bring the plan to life with a highly requested Sentry plugin 🎉
Sentry allows developers to ensure the quality of their applications. It logs errors and gives you all the context you need to identify the source of the problem. Here's a sneak peek of what a Strapi error may look like in Sentry.
This plugin lets you benefit from all these Sentry features with your Strapi app. Once you install it, the Sentry plugin will:
Interested? Check out the instructions on how to use the Strapi Sentry plugin in the article written by Rémi.
In this online meetup, Rémi de Juvigny, Software Engineer at Strapi, and Rohit Kataria, Customer Solutions Engineer at Sentry, walk you through the best practices for an end to end JAMstack Monitoring.
Get access to the recording of this meetup through the form below:
We’re striving to make Strapi a robust and secure tool for all kinds of projects and users. Version 3.5 introduces an SSO authentication feature for the Strapi admin panel, which lets enterprises connect Strapi to their authentication providers and protocols such as Active Directory, Okta, Auth0, Keycloak, OAuth etc. Employees will be able to use the credentials of a third-party app to log in to the admin panel. Please note that version 3.5 includes only SSO authentication and not authorization.
The SSO Authentication feature for the admin panel is available in a Gold Enterprise Edition plan. There are several reasons why we made this decision:
We appreciate every commit and input the community did and continues doing for Strapi, as well as respect all feedback. Our mission is to empower millions of people to share & manage content in tomorrow’s world, and thanks to you we’re getting one step closer to it every day.
We’re also releasing many smaller improvements and fixes contributed by awesome community members. Other highlights from v3.5 and previous releases include:
This improvement lets you set up custom logic to react to particular authentication events. For example, if someone connects to the Strapi application using either Strapi login or 3rd-party service login via SSO, you can set up a reaction to this event - like send a notification or a message to a third-party service. You can also trigger these events if there is an error in the connexion process or if somebody logs in using authorization.
Here are some examples:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
events: {
// Emitted when an admin user has successfully logged in to the administration panel
onConnectionSuccess(e) {
const { user, provider } = e;
console.log(`Connection successful for user n°${user.id} using ${provider}`);
},
// Emitted when an admin user failed to log in to the administration panel
onConnectionError(e) {
const { error, provider } = e;
console.log(`An error has occurred as someone tried to log in using ${provider}`);
console.log(error);
},
// Emitted when a user has been registered thanks to the auto-register feature added by SSO.
onSSOAutoRegistration(e) {
const { user, provider } = e;
console.log(
`A new user (${user.id}) has been automatically registered using ${provider}`
);
},
Read responsive breakpoints from config instead of being hardcoded #9002
Have a look at more fixes and enhancements here, perhaps the bug that has been bugging you is fixed now 🤭
We have a detailed changelog on Github which includes all the new features, bug fixes, and improvements. However, while it’s quite detailed and thorough, it doesn’t provide a quick overview of what’s new in Strapi.
That’s why we’re introducing a new changelog on the Strapi website, which lets you navigate through the history of major Strapi updates in one scroll. You can also access the materials which explain each new feature and release in more detail.
Now you know how to quickly find out what’s new in Strapi 🤓
You can check out our hosted demo with sample data to see what Strapi is like. We also have a template library where you can find starters for a blog, corporate website, portfolio, or e-commerce website using different frontend technologies.
You can also create a new Strapi project on your computer by running the quickstart command:
npx create-strapi-app my-project --quickstart
Follow the migration guides to update your Strapi version and access more features.
Strapi is an open-source product and everyone can contribute to it. The Strapi community helps us move forward and we are making Strapi better with our users in mind.
Here’s how you can help us to improve the product:
Strapi is a product built together with more than 600 community members. We would love to say thank you to people who contributed to the v3.5 release as well to the previous v3.4 enhancements and bug fixes:
@rlvk-vk, @gh640, @Heziode, @Zeranoe, @jozefcipa, @pimsomeday, @darron1217, @Igloczek, @croatian91, @pr0gr8mm3r, @NgyAnthony, @leroydev, @shtelzerartem, @iicdii, @shiningnova57, @jorrit, @jonmol, @csandven, @gh0stsh0t, @centogram, @dappiu, @ertrzyiks, @cwray-tech, @meck93, @taylor-work, @bglidwell, @florianmarkusse, @MattieBelt, @blefevre, @PaulWeinsberg, @tunasakar, ThewBear, @yusufisl, @acalvino4, @avdeyev and @ngjoni.
Join the community! Come chat with us on Forum or Slack, or jump in on Github directly. We're always happy to meet new members of the Strapi family ❤️