I'm not entirely sure if this is the best place to ask, I have dug around the main umbraco site but I don't seem to be able to find any significant information on the planned changes for the Umbraco backoffice? Anything I have found is almost entirely focused on moving ASP.net 5+ (core/standard).
Whilst I understand the many benefits updating to core would provide, not least in the cloud! I wonder why the team has left the backoffice to fester on AngularJS for so, so long? If you consider (if you are to assume Angular is still relevant) it's now on version 11 (renamed Angular framework) and currently the back office is on v1.x of AngularJS. That's a staggering amount of technical debt sat right there!
One thing I do know is over the years I've had to tweak the backoffice considerably for our own projects and having to retain knowledge of a framework which is obsolete is quite a tough ask!
Most of our company projects tend to focus on Vue (which has so far been vastly more compatible version to version compared to Angular) and there's also a lot of interest here in Blazor as it is looking to be a very viable front-end framework that will leverage existing knowledge of the MS Stack.
Not using Blazor for the backoffice will only allow the JavaScript cancer to grow even more. Mainly because you will be maintaining two APIs for the rest of time. It's already pretty much bullshit with prevalueeditors and propertyeditors and the sad state of macros.
What's the future of the Umbraco Backoffice?
I'm not entirely sure if this is the best place to ask, I have dug around the main umbraco site but I don't seem to be able to find any significant information on the planned changes for the Umbraco backoffice? Anything I have found is almost entirely focused on moving ASP.net 5+ (core/standard).
Whilst I understand the many benefits updating to core would provide, not least in the cloud! I wonder why the team has left the backoffice to fester on AngularJS for so, so long? If you consider (if you are to assume Angular is still relevant) it's now on version 11 (renamed Angular framework) and currently the back office is on v1.x of AngularJS. That's a staggering amount of technical debt sat right there!
One thing I do know is over the years I've had to tweak the backoffice considerably for our own projects and having to retain knowledge of a framework which is obsolete is quite a tough ask!
Most of our company projects tend to focus on Vue (which has so far been vastly more compatible version to version compared to Angular) and there's also a lot of interest here in Blazor as it is looking to be a very viable front-end framework that will leverage existing knowledge of the MS Stack.
So what's the plan for Umbraco's back office?
There is a lot going on behind the scenes that's really exciting. You can read more about it here:
https://github.com/umbraco/rfcs/blob/main/cms/0021-future-proofing-the-umbraco-backoffic1e.md
and here:
https://github.com/umbraco/rfcs/blob/0022-ui-library/cms/0022-ui-library.md
Here's the RFC GitHub repo:
https://github.com/umbraco/rfcs
I hope this helps.
There's a couple of recent blog posts that would be useful reading too:
https://umbraco.com/blog/future-proofing-the-backoffice-define-the-extension-api/
https://umbraco.com/blog/join-the-backoffice-community-team/
Andy
Oh wow!
All very interesting stuff.
Many thanks.
Not using Blazor for the backoffice will only allow the JavaScript cancer to grow even more. Mainly because you will be maintaining two APIs for the rest of time. It's already pretty much bullshit with prevalueeditors and propertyeditors and the sad state of macros.
is working on a reply...