The Umbraco Roadmap

This is the second 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: February, 2021

Website rendering enabled. Routing is working and content can be queried and rendered in views.

Members enabled. Allows for the use of the updated member integration for restricting public access to content and using the member API. This has been updated to use .NET Identity. 

Packages enabled: It is possible to register and develop packages for Umbraco on .NET Core.

The beta build will let implementers/frontend developers use and test Umbraco on .NET Core end-to-end.

Expected release: March 2021

We’re introducing a new subscription engine for Umbraco Cloud enabling you to create and manage subscriptions directly in the Portal. 

Expected Release: March, 2021

The deployment engine on Umbraco Cloud, allocating projects, managing multiple environments and transferring changes between environments, will be updated to work in the new infrastructure and new projects created on Umbraco Cloud will take advantage of this. For more details see The Future of Umbraco Cloud blog post.

Expected Release: March, 2021

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: 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.

Existing Umbraco Cloud, Uno and Heartcore projects will be migrated to the new and improved Umbraco Cloud infrastructure. We’ll have detailed information on the migration process when we get closer to the release. For more details see The Future of Umbraco Cloud blog post.

Expected Release: March-April, 2021

Ready for Package Development: 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.

Target release: Q2, 2021

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.

Ready for project development: Umbraco CMS is running on .NET Core is released, official packages are supported and new projects can be developed using the latest version.

Target release: Q3, 2021

Umbraco’s backoffice implementation is currently based on angularJS which is entering EOL in 2021. We want to update the backoffice using a modern approach with a better architecture. The aim is to make life easier for developers, package authors and editors alike.The project is currently divided into three milestones. Each milestone will have separate RFCs:

1. Build a UI Library (January 2021)
2. Define backoffice API (Spring 2021)
3. Implement backoffice (2021)

An RFC for the overall approach can be found here

Allows you to schedule automatic upgrades of Umbraco CMS, Forms and Deploy. You will be given a timeframe in with you can schedule the upgrade to ensure better planning and handling of automatic upgrades

Expected Release: 2021

Taking advantage of new CDN capabilities on Umbraco for serving media and content will enable you to control caching and deliver assets more efficiently. 

Expected Release: 2021

With a new infrastructure in place we can work towards expanding hosting capabilities to include other regions. Starting with a US-based region in addition to the current Western European region.

Expected Release: 2021

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.