Below you’ll find the Umbraco Roadmap, a general, high-level, overview of what the Umbraco HQ development team is working on Now, Next and Later. The Roadmap will give you an idea of where our software products are going and at what state the different components are currently in so you know if your favourite feature is on the roadmap and its current state.
For more detailed information concerning upcoming releases, please see our public release overview.
For an overview of the features and projects that have already been delivered, please see Roadmap History.
Projects/Features that the development team currently have their hands on. You’ll also find an expected launch date/time period on most of the components.
Projects/Features that we have started the process of planning. Once the necessary planning and preparation is done, this will be moved up to “Now” where it will be given an expected delivery time and, in some cases, split into smaller components.
Big projects that are on the team's “future board”. As work starts on the "Later" projects, they'll be broken up into smaller components before going into the "Next" level.
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 release: July 29, 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: June, 2022
With Umbraco Id added to all existing and new Umbraco Heartcore projects we are enabling 2-factor Authentication (2FA), so users of the backoffice and Umbraco Cloud Portal will be prompted to provide an auth code (sent via email or text message) after having entered their username and password.
Two-factor Authentication will be an opt-in feature on a per user basis.
Target release: Q3, 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
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.
Target release: July, 2022
Adding details of workflow completion to back-office with possibility of re-try. Provision of additional data to workflows from rendering partial.
Target release: July, 2022
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.
Target release: June, 2022
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.
Target release: Q4. 2022
Together with a huge amount of project info, a slim project representation, and a filtering system, you will see a much-improved overview for managing all your Umbraco Cloud projects. Flexibility and usability is the focus in enabling Umbraco Cloud to empower users to organize and group their projects.
Target release: Q3, 2022
Creation of an integration and updates to the Forms product itself to support receiving payments, using a hosted page provided by a payment provider.
Target release: July, 2022
Once a new extension API has been proposed and accepted through the RFC process, implementation can begin in collaboration with the Backoffice Community team.
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.
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.
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.
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.
REST API endpoint for retrieving list of changed urls - the ones from the redirects dashboard in the Umbraco Backoffice
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.
We'll investigate if Entity Framework is a viable Object Relational Mapper and can replacement for NPoco. NPoco has done a good job but, if possible, we want to benefit from the broad usage of Entity Framework, its support and its alignment with .NET core versions which we believe will introduce a more standardized development process.
We'll introduce a headless API based on Open API in close collaboration with the Heartcore team, so that our API's share the same schema. This way we'll add "out of the box" headless functionality including a hybrid mode in the core CMS while making it easy to move from a standard installation of Umbraco to Umbraco Heartcore.
We want to make variations available on the Block level, so that we e.g. have better support for multiple languages in blocks - whether it's in the Block List Editor or in the Block Grid Editor.
Together with the Umbraco Heartcore team we'll introduce webhooks in the core CMS, so that clients can be notified when changes happens in the Umbraco backoffice. This functionality will introduce callback functionality within the core CMS but also make it easier to later migrate to Heartcore.
One of the biggest benefits of using Umbraco is that we have the friendliest Open Source community on this planet. A community that's incredibly pro-active, extremely talented and helpful.
If you get an idea for something you would like to build in Umbraco, chances are that someone has already built it. And if you have a question, are looking for documentation or need friendly advice, go ahead and ask the Umbraco community on Our.