StrapiConf, the second global annual user conference for the Strapi community, is happening today. Traditionally, the Strapi team announced the awaited product updates and shared the product vision. Read on to learn more!
When building the marketplace, we focused on three principles: security, quality, and openness. Our users must know that they can safely use any plugin they would find on Strapi Market; that’s why our team always does a security check before displaying anything.
We review the code and the design of the plugins to make sure Strapi users have the best and most consistent experience, and we add a validation check to the ones following all of our guidelines.
Finally, we want to make sure anyone can submit and suggest new plugin ideas. So now we have it: a place for the Strapi ecosystem to share and find new integrations.
Introducing the in-app marketplace. Everything you love about the market directly in Strapi. Now you can find all the plugins you need right in the app.
The in-app marketplace is available in the new version Strapi 4.1.4. Please read the release blog post to learn more about it!
We are pleased to announce the release of the migration guides from v3 to v4. As you may know, we only supported SQL databases for now on v4. For MongoDB users on v3, we will also have a dedicated guide for you to switch from a v3 MongoDB to a v4 SQL project coming very soon. Then, you can follow the v3 SQL to v4 SQL migration guide like the others.
To make it easier and faster, especially for projects with a lot of data, we are working with our partner Notum to develop migration scripts to help make the process even easier. They should be ready by early April.
Soon, we will release Strapi v4.2, including one of the most requested features: Dark Mode.
You can easily switch between the dark and the light mode through the user profile section in the administration panel. This new functionality also sets the foundations for future more advanced and custom themes.
As we did on the Strapi Design System, we made a lot of efforts to make it highly accessible for people with special needs by providing high contrasts. We reached an AA accessibility level.
To test the beta version of the feature, please run the command npx create-strapi-app@beta my-app (--ts)
Feedback always is welcome; please share it on the forum!
Strapi v4.2 will also bring the most voted feature on our public roadmap: TypeScript support.
As a developer, you can now create and write lines of code using TypeScript files. All these files will be automatically compiled during the development phase. We updated the Webpack configuration and yarn develop
command in our CLI to support this new feature natively. If you want to update these configurations, you’ll be able to do it through a tsconfig.json
configuration file.
When we developed Strapi v4, we anticipated TypeScript support by introducing an internal typing system. This new TypeScript support relies on it, but it will also be very useful for schema & data migration.
To test the beta version of TypeScript support, run the command npx create-strapi-app@beta my-app (--ts)
in a terminal.
What is Strapi missing to take customization to the next level? You know the answer: custom fields.
This feature has several purposes. The first one is obviously to support more types of fields. We looked at your projects and there is always a case when you have business data coming from an external source, or you want to pin a location on a map, or a customer needs a custom video player, and so on. Custom fields are the answer to your custom needs.
They also improve the content editing experience by displaying the content differently in the administration panel. If you are migrating from an existing CMS, we know that you often want to offer a similar user experience. Something they are used to. With the custom fields, you can reproduce a familiar content editing experience with Strapi.
Finally, under the hood, the custom fields are a powerful way to aggregate APIs. Imagine you have a product field. The data is coming from a Shopify store. You pick a product from Shopify and link it with an entry in Strapi. Once you fetch the entry, you will also be able to retrieve the data from Shopify and aggregate the data with a single API call. It will significantly speed up the development.
To make this new initiative a success, we need YOU. We just opened new custom field RFCs, a non-technical and a technical one that describes in detail the scope of the first iteration. Any comments and help are welcome.
Our unique ambition behind Strapi Cloud is to provide the easiest way to deploy Strapi projects. The Developer Experience really matters here, and offering a seamless deployment process that requires absolutely no DevOps skills is our top priority.
We chose a Platform-as-a-Service approach to double down on what makes Strapi unique: its customization capabilities. Strapi Cloud will allow you to start your project locally, customize it according to your needs, version it through Git, and deploy it in seconds.
We plan to offer automatic backups, a global and fast CDN, multi-database support, and more. All of these features will come incrementally.
We also plan to offer a free tier, so everyone can benefit from this frictionless experience.
Regarding timeline, we plan to enroll a limited number of users on the alpha version this year. We'll then launch an official beta program with hundreds of users and partners.
General Availability is planned for 2023. We will share more details throughout the year. In the meantime, we invite everyone interested in being a beta tester to join the waitlist.
We always consider your opinion when creating the roadmap and prioritizing the next features we should work on. Each vote, comment, and insight count! Please let us know how we can make Strapi a better product for you.
Strapi is free and easy to use; give it a try! To create a new Strapi project, just run the following command:
npx create-strapi-app my-project --quickstart
Follow the Quick Start Guide for detailed step-by-step instructions or have a look at a video instruction:
You can also use a demo project to test the content editing experience. To do that, fill out the form, and you'll receive a link with access.