Simply copy and paste the following command line in your terminal to create your first Strapi project.

Get Started

Today, the Strapi team is very excited to announce [StrapiConf](https://www.strapi.io/strapi-conf-2021), a virtual conference that will take place on **April 22nd, 2021 from 9 am to 3 pm PST**, a time slot that we think is the most inclusive of all timezone and geographical locations. 

![gif](/uploads/gif_4260ca12cc.jpeg)

With this **free and virtual conference**, our intention is to bring together all the Strapi users, contributors, customers, and partners from all over the world for a day filled with Strapi learning, collaboration, and networking opportunities. 

From Strapi basics and Headless CMS best practices to insights into how to quickly build JAMStack websites, Mobile Applications, and modern digital experiences, StrapiConf will include content for everyone. Looking out a little further, we’ll share our vision for making Strapi a key enabler of the next revolution of low-code application development, taking advantage of APIs.

No matter your level of expertise with Strapi, Headless CMS in general, or your job title, attendees will get unique opportunities to learn and collaborate with their peers at other companies using Strapi to build modern, content-driven applications. 

The conference will include **2 tracks**, with  **30m talks** and  **10m lightning talks**. The first track will be geared towards **advanced users** and include **technical** Strapi concepts, customer/user stories, and integrations. The 2nd track will be for **Strapi beginners**, **Product and Content Managers**. 

The official schedule will be published in **January** but you can already [pre-register](https://www.strapi.io/strapi-conf-2021) and [submit proposals](https://docs.google.com/forms/d/e/1FAIpQLScUYkXm67c-yHccRYsskeUMWO4uwoWtFsBBElmVlrFYYfUyow/viewform) today! 

Please share the love on Twitter by following [@strapijs](https://twitter.com/strapijs) with the hashtag #StrapiConf and don’t hesitate to reach out to [conf@strapi.io](mailto:conf@strapi.io) if you have any questions. 


---

Get started with Strapi by creating a project, using a starter or trying our instant live demo. Also, consult our forum if you have any questions. We will be there to help you.
<p align="center">
<a href="https://strapi.io/documentation/developer-docs/latest/getting-started/quick-start.html#_1-install-strapi-and-create-a-new-project">
<img src="https://assets.strapi.io/uploads/Get_Started_e4e026ce55.svg#small" />
</a>
<a href="https://strapi.io/starters">
<img src="https://assets.strapi.io/uploads/Starters_9da222d819.svg#small" />
</a>
<a href="https://strapi.io/demo">
<img src="https://assets.strapi.io/uploads/Try_live_demo_af11161cd6.svg#small" />
</a>
</p>
<p align="center">
<a href="https://academy.strapi.io">
<img src="https://assets.strapi.io/uploads/Strapi_Academy_9ff315144a.svg#small" />
</a>
<a href="https://forum.strapi.io">
<img src="https://assets.strapi.io/uploads/Forum_3ab5cad74b.svg#small" />
</a>
</p>
See you soon!

The Ecosystem section covers everything related to the world of Headless CMS and Strapi's place in it. 

Ecosystem

Blog Cover Strapi Conf (2)

Announcing the first Strapi global user conference! It's a one-day conference for the Strapi Community to learn, contribute, and collaborate on the future of the leading open-source Headless CMS.

The Product section covers our releases, feature reviews and more. 

Product

The Tutorials section covers an introduction to Strapi, some advanced technical content, product updates and releases. From basic workaround to in-depth development guides. 

Tutorials

The latest Strapi-related news and major events happening for Strapi – including announcements, remote-work, organization and tips on running a start-up. 

Company

Get all the latest updates, news and events.

Subscribe to the newsletter 📣

We recently updated the public roadmap. In this article, Strapi CPO Aurélien will give you as much explanation as possible about this. 

Strapi_Road_Map (1)

We've Updated Our Roadmap

In this article, you will learn about all the recent updates in Strapi during the summer: New members in the team and the new features for the product. 

Summer_Updates

Strapi Summer Update

Winter is coming, but there are new hot features in our hood! 
Let’s jump in this Monthly Update to learn more about Strapi news in the last quarter of 2020. 


Monthly Updates

Monthly Update November 2020

You may have noticed that we've recently updated our public roadmap. In this article, I'm going to explain the reasons behind this ** "unexpected" **update. Running a public roadmap is full of challenges, some of them were impossible to tackle, it was time for changes!

The main goal of having a public roadmap is to give as much visibility as possible to digital agencies, freelancers, free users, or customers. We truly wanted to share our internal planning for features development but we hit some roadblocks.

As an **open-source project**, a lot of bugs are fixed on a daily basis. Thanks to the amazing contributions we receive, there are issues that are fixed quicker than expected. Sometimes we also work on the same functionalities which are simultaneously being developed by a community member. Not very productive. We have to admit that, there is room for improvement in the way we collaborate with the Strapi community and ecosystem. Until we have completed the UX research and feature scoping, we cannot give a precise date and guarantee that a feature will be delivered on time. 

In the last 12 months, we have done a decent job at shipping most of the features on time, but the community deserves a more accurate and tangible roadmap. Recently, the team grew and the way we were managing the roadmap was incompatible with our new work organization and the community's contributions.

The launch of the [Enterprise Edition](https://strapi.io/enterprise) was the last missing proof that the way we've managed the roadmap in the wrong way. As the roadmap is public, we are accountable for what we put in it. We cannot move a feature from a quarter to another without giving explanations. We know that a lot of you respond to requests for proposals, or have roadmaps which depend on ours.

As a reminder, the Enterprise Edition shares the same codebase as the Community Edition one without the limitations. Currently, the only difference between both is **the number of roles** and **the granularity in their customization capabilities**. We are trying to understand how the users and enterprises use Strapi to define a boundary between both. Nothing is written in the stone and we are open to suggestions to make the best decision.

To improve the way we communicate about the future roadmap changes, we decided to rethink our strategy from scratch. We want to create and define a roadmap that you trust just as much as we trust it.
One of the misconceptions about roadmaps is that we can predict everything. The future is, will stay always uncertain. Our goal is to share with you **an honest roadmap**.

![Untitled (1)](https://api-prod.strapi.io/uploads/Untitled_(1)_4d7d381e83.png)
Source: https://twitter.com/PavelASamsonov/status/1296818042928861184?s=20

Our first decision made was to postpone the features by 3 months. To be **100% transparent,** we expect to release some of them in advance but we prefer to ship earlier than later.

Then, we decided to simplify the overall roadmap, we've started to create categories such as "Maybe in 2021..." to tell you that you shouldn't count on us to release the feature on time. It was our way to say: "It's not the priority, we lack resources, we are not ready.." The roadmap only contains features that we are working on and which are truly in our backlog.

We also wanted to include the technical roadmap within the public roadmap. Most of the features are delayed for technical reasons. For instance, the Internationalization hugely depends on our ability to ship the new Database Layer Refresh and Plugin API on time. These topics are massive and hard to scope. By doing so, we expect to increase the visibility and the "why" behind each feature.

Last but not least, we upgraded our **productboard plan** to enable more features to be able to collect more insights from you. It will also let us reorganize in a brand new way, introduce naming conventions, and identify what are your expectations.

These are the first steps of an iterative process designed to help you build successful projects and businesses with Strapi. There are more to come. For instance, we plan to improve and open our development workflow to work closely with you (the community) or introduce a **long-term support strategy.**

## Learn more about Strapi:
- Check out [the public roadmap](https://portal.productboard.com/strapi/1-roadmap/tabs/2-under-consideration)
- Try the [latest version of Strapi](https://strapi.io/documentation/v3.x/getting-started/quick-start.html)
- Learn about [Strapi features](https://strapi.io/features)


Summer (in Europe) just started a month ago, even if we would like to enjoy the lovely weather, the core team and contributors worked hard to provide a bunch of updates and enhancements. From the [Enterprise Edition](/enterprise) to the new [Role-Based Access Control feature](/blog/announcing-3.1-role-based-access-control), the Strapi ecosystem is booming! Let's see this in details below 👇
 
Unfortunately, there has been no online meetup scheduled in July, but don't worry, we will back soon with new formats and even more meetups! Nevertheless, last month, Jeff Meyerson interviewed Pierre (Strapi's CEO) about our product, what is our mission, and the new Headless CMS trend in [Software Engineering Daily](https://softwareengineeringdaily.com/2020/07/10/strapi-headless-cms-with-pierre-burgy/).
 
 
## Company
 
We are thrilled to welcome **Victor** as Customer Success Manager, **Rémi** as Software Engineer, **Daniel** as Developer Advocate, **Samuel** as Product Manager (community-oriented), **Mégane** as Technical Writer and **Anastasiia** as Product Marketing Manager! Victor will help our customers get the most out of Strapi to ensure they successfully reach their business goals, while Rémi will develop new starters to help our users to set up new projects in no time. Talking about starters, Daniel will promote them and the whole product to everyone by participating and attending a lot of conferences and meetups. Feel free to say "Hello 👋", you won't regret it, he's awesome! And last but not least, Samuel will help you as a community member to contribute more and more to the project by improving the collaboration between the core team and contributors, Megane will make the documentation as easy to read as 1,2,3 and Anastasiia will tell you all about what’s coming next and the latest Strapi features.

![newStrapiers](https://assets.strapi.io/uploads/newStrapiers_b0c0966b24.jpeg)
 
 
Oh, I almost forgot him because he was already considered as part of the team, our one and only **[Derrick](https://strapi.io/blog/welcoming-derrick-to-the-strapi-team)**, one of the most active contributors, joined the project as a Solution Engineer last July. He will continue to help everyone find solutions to their issues! We wrote a [dedicated post](https://strapi.io/blog/welcoming-derrick-to-the-strapi-team), check it out!
 
 
We are still looking for new awesome people to join the team. If you want to be part of the journey, send us your [application](https://strapi.io/careers)!

 
## Product
 
Every year, we try to define two milestones at the beginning of the year. This year, one of these was the development of the [Role-Based Access Control feature](https://strapi.io/blog/announcing-3.1-role-based-access-control). As a CMS providing an administration panel, it is mandatory to be able to define the permissions to access specific features. We already received a lot of feedback from the community, they are really good and we couldn't expect a better way to start the summer!
 
This new release was also an excellent opportunity to officially start (in ßeta) the first part of our business model. Following the common open-core model, we are now offering an Enterprise Edition of Strapi. In this edition, you've unlimited access to **Role-Based Access Control**. It also offers exclusive advantages such as customer support and training.
 
If you want to know more about the Enterprise Edition and the [pricing](https://strapi.io/pricing), please read the [official press release](https://strapi.io/blog/introducing-strapi-enterprise-edition-beta-and-plans).
 
Even if summer often rhymes with holidays on the beach, our core developer team is happy to work on developing new features just for you!! Here’s [the roadmap](https://portal.productboard.com/strapi/1-roadmap/tabs/2-under-consideration):
 
- Draft & Publish
- Contributor License Agreement (CLA)
- Plugin API
- Database Layer
 
### Draft & Publish
 
As an **open-source company** and **headless CMS**, our obsession has always been to provide the best developer experience possible. However, once the project is set up, developers hand the projects to the final end-users: the Content Editors. Their goal is to write the best and creative content possible. In order to do that, they need time to think, test, and iterate their ideas.
 
That's why introducing a real draft system was absolutely necessary. Being able to write content, step away, and come back to continue writing is impossible without a drafting feature. The Draft & Publish system will also include another principle: **collaboration**. We don't want to let a user override the content written by another user, even more, when a second user is editing it at the same time. In order to do that, the feature will provide a "Take over" functionality to alert users when another user is already editing an entry. If they want to, they’ll be able to take over the entry to edit it.
 
We plan to release the feature at the end of the quarter, in September.
 
### Contributor License Agreement
 
When we contribute to the project, like any contributor, we have to sign every commit to ensure the DCO robot will accept the PR. Even if the DCO is the lightest way to ensure every commit's author has the right to submit its changes and let everyone use them, the overall process can be painful.
 
To fix that, we decided to ask every contributor to sign a CLA once for all to make the contribution workflow easier. The CLA document will be very close to the DCO one. We plan to use the [CLA assistant](https://github.com/cla-assistant/cla-assistant) open-source library developed by SAP. In other words, it means that as a new contributor you'll have to sign the CLA, otherwise your pull request won't be merged. Then, for the next contributions, you won't have to repeat the process as a CLA isn't associated with the code itself but to a person.
 
### Plugin API
 
Regarding what's coming next in the roadmap, especially the Internationalization feature, we had to invest time in the internal APIs. As we plan to provide this feature as a plugin, we need to continue the development of the Plugin API.
 
More specifically, the Plugin API should provide an abstraction layer to do the following actions:
 
- Inject dependencies
- Add new command in the CLI
- Add new controllers, models, and services
 
In the next few months, we will open an RFC to share the details of the Plugin API implementation.
 
### Database Layer
 
If you are familiar with Strapi, or if you take a look at our [public roadmap](https://portal.productboard.com/strapi/1-public-roadmap/tabs/3-planned) or [issues](https://github.com/strapi/strapi/issues), you know that our current filter system can be optimized. Thus, we also have performance issues in our GraphQL plugin. By harmonizing the way we deal with data and how we filter it, we want to increase the productivity of the core team but also of everyone writing custom code in their Strapi projects.
 
Like the Plugin API, we will come back to you with further details soon.
 
## Conclusion
 
I hope this post has given you more visibility of what we have been doing this summer. If you have any questions, feel free to post a comment below. We look forward to answering you!
 
See you soon 👋


Winter is coming, but there are new hot features in our hood! Last quarter was dedicated to the Draft & Publish feature and several other releases, but, you won’t be disappointed with this last quarter of 2020. For the holiday season, we are cooking a few specialties that will truly tempt your tastebuds! Let’s jump in this Monthly Update, I know you’re hungry for more 😋

![source](/uploads/source_a1268ff473.gif)

## Company 

We’ve recently opened three different job positions within the Product team. I strongly recommend you to give a look at the job descriptions, we are living through exciting times at Strapi, the Headless CMS space is moving fast, the company missions are extremely interesting and challenging! 

- [Product Manager](https://www.welcometothejungle.com/en/companies/strapi/jobs/product-manager_world)
- [Senior Product Designer](https://www.welcometothejungle.com/en/companies/strapi/jobs/senior-product-designer_world)

We also have many open positions in other teams, you can check all the open opportunities [here](https://www.welcometothejungle.com/en/companies/strapi/jobs).

## Product

### Draft & Publish
As you might have noticed, we released the highly awaited Draft & Publish feature. See the [great announcement article](https://strapi.io/blog/announcing-a-new-draft-and-publish-feature) written by Anastasiia. The feature release is a success, we have already seen that more than 70% of the new users adopting the feature. Last week, 24% of the created entries used the new draft & publish publication flow! 

This release was also the last step of the plugin settings migration into a single location on the dashboard. We’ve started the migration process in Q2, 2020 when we introduced the Role-Based Access Control functionality. 

Moreover, I would like to highlight the new templating system developed by Rémi, our Software Engineer in charge of Integrations. With these templates, you will be able to start a new project using an existing data structure and feed that structure with real content. 

If you want to know more about the templates, [go check out this page](https://strapi.io/documentation/v3.x/concepts/templates.html#templates) or give it a try by copying/pasting the following command in your terminal, you won’t be disappointed!

```
yarn create strapi-app my-project-template --quickstart --template
https://github.com/strapi/strapi-template-corporate
```

### Relational Fields
A bit less [than three hundred](https://portal.productboard.com/strapi/1-roadmap/c/49-display-relational-field-in-list-view) community members asked to display relational fields in the list view of the content manager. We’ve listened to you and we’ve started to develop this enhancement. It should be released by the end of the year. 

![Screenshot 2020-10-29 at 15.49.28](/uploads/Screenshot_2020_10_29_at_15_49_28_3cc41a3376.png)

### Single Sign-On (SSO) — Authentication
In July, we introduced the [Enterprise Edition](https://strapi.io/blog/introducing-strapi-enterprise-edition-beta-and-plans) of Strapi. The feedback was positive, except on the pricing that we recently updated to offer a much more affordable plan [starting at $29/month](https://strapi.io/blog/introducing-bronze-plan-new-hosted-trials-and-starter-library). Thanks to the Enterprise Edition, we’ve started to have not only users but customers. We discovered that many of them see the lack of SSO support as a potential deal-breaker. Even if we will always be a community-centric and product-driven company, we’ve decided to go a step further and partially develop the SSO feature to test out our business capabilities. 

The SSO will be limited to the authentication part only. In other words, as enterprise users, you’ll be able to** set up an Identity Provider** such as Okta, Auth0, or any kind of authentication server compatible with SAML. As our authentication system is mainly based on Passport.js, all the community packages offered by the Passport.js community will be compatible with our system. This partial feature will let you manage your users through your IP without requiring any handling in the Strapi dashboard.

Later, we will continue to invest in the SSO functionality by bringing an authorization layer to easily manage the permissions via the Identity Providers.

*Reminder: the feature will be only available for Enterprise Edition users.*

### Internationalization
We are entering the latest phase before starting the development in mid-November. The feature will include a large scope of functionalities such as:

- Internationalization (en_EN, en_US, en_CA).
- Internationalization per field.
- Set different locales per content-type.
- Default fallback (always returns the default local entry value).
- Copy content from a chosen locale.
- Locale renaming.
- Each translation lives as a different entry.
- Concurrent editing support (avoid two people working on the same translation, but they can work on the same entry).
- Publish one translation or all of them.
- Draft & Publish publication flow support.

The Enterprise Edition will have two more features :

- Fallback chain (create a chain of translation fallback per content-type).
- Role-Based Access Control support (restrict the rights of a role to a specific locale).
- An unlimited number of locales.

Internationalization will be included in every plan starting at $29/month. If you’ve any questions or insights, feel free to use the [Forum](https://forum.strapi.io/) or comment on this post below, we are open to suggestions.

*Note: the feature will be delivered in two iterations. The two releases are expected in Q1, 2020. The first one won’t include the fallback chain functionality.*

Also, we will have to introduce breaking changes at the API level to support this new feature. Even if the Internationalization will be served as a plugin, to keep the API consistent, we will have to update all the current APIs exposed. This means the Internationalization will be introduced in a new major version of Strapi (v4). 

## Conclusion
All good things must come to an end, we are doing our best to deliver all the announced features on time for the last quarter of the year. In the next post, I’ll explain to you what’s coming in 2021, mostly technical investments, fixing architectural issues, and internal APIs to develop the ecosystem.

Thank you for reading, take care of yourself and your closest ones. See you next month!

**Learn more about Strapi Enterprise Editions**

- Request a [free 30 day trial](https://strapi.io/pricing)
- [Contact Sales](https://strapi.io/enterprise#contact)
- Find a [Strapi Partner](https://strapi.io/partners)

Winter is coming, but there are new hot features in our hood! 
Let’s jump in this Monthly Update to learn more about Strapi news in the last quarter of 2020. 

You might be also interested in 

Get all the latest Strapi updates, news and events.

Join our Newsletter

Announcing StrapiConf - Our First Global User Conference

victor_coisne

Victor Coisne is VP Marketing at Strapi, the leading Open Source Headless CMS. As an open-source and developer community enthusiast, Victor has been working for Open Core B2B companies for more than a decade including 5+ years as Head of Community at Docker. In his free time, Victor enjoys spending time with friends, wine tasting, playing chess, tennis or soccer.