The Umbraco Roadmap

This is the first stage of an easier account handling for your Cloud projects and will open up possibilities for vastly improved integrations and best practice account features such as two-factor authentication.

Expected Release: Q4, 2020

The ability to use Umbraco Cloud Deployment technology outside of Umbraco Cloud to ease deployment between multiple Umbraco environments by connecting external hosted Umbraco projects with localhost or Umbraco Cloud as Development environments.

Expected Release: Q4, 2020

Content can be queried and rendered in views. With this ready we can release a beta build and implementers/frontend developers can start using and testing the .NET Core. This milestone should produce a beta build.

Expected release: Q1 2021

With persisted queries you can define and save your GraphQL queries up front, so you only allow pre-defined queries to be executed against your Content. Another benefit of having persisted queries is that the popular Apollo GraphQL client library supports this approach and will thus send a hash instead of the entire query, which might be a a big payload to send multiple times, so a lot less to send across the wire.

Expected release: November, 2020

Round 2 of improvements to the Rich Text editor. Focus will be on more dynamic/responsive image handling along with improved configuration.

A Request For Comments has been accepted on this topic on GitHub. You can see it right here

With the launch of Umbraco Uno you are limited to one theme. We will introduce several inspirational themes with broader use-cases and a wider set of configurations to best suit your needs.

Umbraco Uno will be enhanced with support for multiple languages in the editing interface of the backoffice. This will make it easy to work with content variations over several languages on your site.

Import changes with a single click, giving you easier manual control and providing more information, directly in the backoffice.

With the first stage of this project you will get:

• Reduced memory overhead for an Umbraco website
• Improved performance of "Cold Boot" scenario when NuCache files do not exist and the in-memory content cache needs to be built from the database
• Ability to swap out Umbraco's default implementations of various front-end content caching services by introducing better abstractions

This will provide a faster and leaner Umbraco CMS both in terms of start-up and ongoing footprint of a running website. You can follow the ongoing work on the issue tracker.

Expected release: December, 2020

Umbraco CMS is running on .NET Core and we can start focusing on the add-ons and packages that will need to be upgraded such Umbraco Forms and Deploy. At this stage we want to get the first release candidate out and this is also the perfect time for package developers to test their package on this new version.

One of the strong features of the Umbraco Backoffice is the ability to extend it with custom Property Editors to fit the needs of the Content Editors. This feature will enable for Umbraco Heartcore as well.

With this feature, you'll be able to configure how many versions (revisions) of content is stored in the Umbraco database. You'll be able to control this on a per document type level and configure how far back versions should go. This will have a positive effect on performance. Especially for sites with a lot of activity and a lot of content.