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.
With this new feature, your content editors will get a better overview of the usage of various media items (images, pdfs etc.) across the created content. This makes it easier to do editorial changes based on the media items used, without having to search through all content or remember where you’ve used your media.
A Request For Comments has been accepted on this topic on GitHub. You can see it right here
Expected Release: 31st of March 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: Q2 2020
A new back-office editor that handles common page structure editing in a simple and intuitive way. The main concept of the editor is to manage list of blocks that represents 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.
This editor aims to be an alternative to the popular editors in Umbraco version 7 such as the Grid, Stacked Content, LeBlender and Doc Type Grid Editor.
A Request For Comments has been accepted on this topic on GitHub. You can see it right here
Umbraco source code solution is re-structured and everything is .NET Core compatible. This first phase in the transition to .NET Core provides a cleaner architecture and makes it easier to work with and contribute to Umbraco. For detailed information information see the Project Structure for Project UniCore RFC.
Backoffice is fully operational on .NET Core. We can build a version that can be end-to-end tested for content management. The plan is to make an alpha release once we reach this milestone.
Being able to preview content in the right context is an important tool for content editors and this feature will make it possible to integrate content preview functionality through a Preview API.
Aside from the Rest API and client libraries, this feature will expand options for consuming content by providing native support for the Graph QL querying language in Umbraco Heartcore projects.
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.
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
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.
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 advise, go ahead and ask the Umbraco community on Our.