The Umbraco Roadmap

Release of an extension for Umbraco CMS supporting a product picker for the Shopify commerce platform. This is part of our Composable DXP (Digital Experience Platform) strategy.

Target release: May 2022

On the road towards custom editors in the Umbraco Heartcore backoffice, we are starting with custom editors for the Grid. Grid editors are simple additions to the Grid, which will be possible to create via the backoffice. A Grid Editor will be created using HTML/javascript/CSS and Web Components, which enables developers to tailor the editor experience of the Grid in Heartcore.

Target: Q2, 2022

Umbraco will ship with the latest version of the .NET framework .NET 6 (and ASP.NET 6) which adds new features such as support for C#10.

Target release: June 16, 2022 (as part of Umbraco 10)

Adding support for SQLite in order to have an embedded database, cross-platform database available in Umbraco CMS. As with SQL CE, in previous versions of Umbraco, this is mainly for development purposes and has the benefit of adding easy cross-platform setup.

Targeted for release with Umbraco 10 in June 16, 2022.

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.

Target release: Summer, 2022

Build of an Umbraco package consisting of a Content App that will integrate with the Google search console URL inspection API, presenting information to allow developers and marketeers to debug and optimize their pages.

This is part of our Composable DXP (Digital Experience Platform) strategy.

Target release: May, 2022

With Umbraco Id added to all existing and new Umbraco Heartcore projects we are enabling 2 Factor Authentication, so users of the Backoffice and Cloud Portal will be prompted to provide an auth code (sent via email or sms) after having entered their username and password.

Two-factor Authentication will be an opt-in feature on a per user basis.

Target release: Q2, 2022

Upgrade your Cloud Projects to run on dedicated hardware. There are multiple tiers to choose from depending on your project plan. The dedicated tiers offer all the features of the shared plans, but with enterprise-scale capacity for Umbraco solutions with demanding workloads.

Target release: Q3

Once a new extension API has been proposed and accepted through the RFC process, implementation can begin in collaboration with the Backoffice Community team.

This is Part 3 of Future-proofing Umbraco's backoffice.

We'll introduce a new Umbraco demo site that showcases the backoffice and gives an introduction to what can be build with Umbraco out of the box. Our goal is to open-source the project, so that it can be used as an easy start for experiments and learning.

An improved overview of your Cloud projects in the Umbraco Cloud portal to improve project management. 

Target release: Q3, 2022

Begin the development of a new API and web presence for Umbraco packages, replacing and combining the existing features on umbraco.com and our.umbraco.com. Will support Umbraco 9+ packages, integrate with NuGet as the primary source for package information and provide a login for package owners to augment their listing. This is part of our Composable DXP (Digital Experience Platform) strategy.

Build of an Umbraco extension to provide a connector with Zapier, allowing triggering of tasks following CMS publishing events and/or form submissions. This is part of our Composable DXP (Digital Experience Platform) strategy.

As part of this feature, we will be adding a new version of the REST API, which will be based on the Open API standard (https://www.openapis.org/). The first iterations of the current REST API are based on the HAL standard. By moving to OpenAPI you’ll see several improvements such as a reduced amount of metadata in the JSON response and improved performance. Open API is a widely known standard with lots of tooling, which we believe will benefit Heartcore and our users.

Target: Q3, 2022

We want to enhance the developer experience by introducing a secure way of storing secrets. A secret can be a connection string, credentials for a service or some other sensitive information to be used by the Umbraco CMS.

In order to support sites with many languages and content editors working with only a subset of the languages, it will possible to set the languages that a User Group can edit.

A useful enhancement for setups with many forms - utilizing the recently introduced feature of grouping forms in folders to allow selection of forms by editors using the folder structure

Adding details of workflow completion to back-office with possibility of re-try. Provision of additional data to workflows from rendering partial.

A new Property Editor that can be a future substitute for the existing popular Grid Layout editor.
The new Property Editor will be based on the Block Editor technology that is used in the Block List editor.

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 by creating Property Editors through the backoffice using html/js/css and WebComponents.

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.

In an effort to make it even easier and faster to get started in Umbraco Cloud, we will add the option to pick a starter kit(s) that will be pre-installed with your new cloud project.

Allow for partners with Umbraco integrations to provide potential customers with the ability to run a trial on Cloud pre-installed with their package and supporting content. This is part of our Composable DXP (Digital Experience Platform) strategy.

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.

As part of this feature we will make API Keys independent of backoffice Users. Currently, an API Key is created for a backoffice User, so the key will get the same permissions as that user.

With this feature we will enable the creation of API Keys and setting permissions on a per key basis. We believe this will make it easier for developers to work with and more secure, as the key is not tied to a specific backoffice user.

In addition to the current configuration options for Webhooks, we’ll be adding the option to specify security headers for the endpoints, which are called. The intention is to add flexibility around the configuration options for webhooks, and being able to call into secured endpoints.

Enhancements to the current queue functionality to support selection for restore and scheduled deployment of content to the upstream environment.

Adding progression display to default theme and inclusion of an optional final confirmation page for review or edit of the pending form submission

Allowing for payment to be handled by others than the project creator.