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, projects etc. 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.
A shared component library for building Umbraco products and packages based on web standards. The UI library is available on Github and open for contributions. Documented using Storybook.
This is Part 1 of Future-proofing Umbraco's backoffice and is detailed further in the UI Component Library RFC (request for comments).
Target release: Q4, 2021
Uncovering the current APIs for extending Umbraco’s backoffice and defining how this should work in the future in order to provide a standardised extension API. This work is being done in collaboration with the Backoffice Community team and will result in an RFC (request for comments) detailing the new proposal for the extension API.
This is Part 2 of Future-proofing Umbraco's backoffice.
Update: The RFC has been published - join the discussion in the RFC for new extension API.
Target for closing the RFC: November 12, 2021.
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.
Target release November 18th with Umbraco 9.1 and later 8.18.
Makes it easier to transfer all items in a section by adding the ability to not only queue and transfer items on a per node basis but also queue an entire tree for transfer. Useful if your site contains multiple root nodes
Target release: November 16, 2021
Allow for better statistics on use of packages in Umbraco CMS. This will help increase understanding of package use, can help improve discoverability and will be opt-in for community/3rd-party packages.
Target release: Q4, 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.
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.
The Block Editor functionality is similar to the one introduced in Umbraco 8.7 and allows you to structure the content in your Heartcore backoffice in a new way. The main concept of the editor is to manage lists of blocks that represent a web page's structure, where each block is both a collection of content and a way to configure that collection to be rendered. Each content block and configuration is defined by an Element Type to make administrating and editing with the new Block editor consistent.
The functionality will first be made available for new Umbraco Heartcore projects and then enabled for existing projects.
Once a new extension API has been proposed and accepted through the RFC process, implementation can begin in collaboration with the Backoffice Community team.
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.
Taking advantage of new CDN capabilities on Umbraco for serving media and content will enable you to control caching and deliver assets more efficiently.
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.
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.
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.
New feature for Umbraco Forms that makes it possible for editors and administrators to edit entries submitted through Umbraco Forms.
The backoffice interface for Umbraco Forms will be updated to use translatable components. This will make it possible to localize Umbraco Forms based on the language of the current user.
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.