Thanks for your answer. What I asked for was more like a discussion of different solutions, examples, cool tweaks and so on both for frontend and backoffice. I'm aware of that I can do the frontend however I want and that the backoffice is developed with AngularJs.
What we have done is that we use a custom controller that replaces the default MVC controller.
The controller calls a mapper we have built to generate a JSON response for the specific url.
If its an initial request we response with html including the bootstrapping code for Angular 9+ including the page json in a script tag to avoid the extra request to load the JSON, the inital request also contains json for the header and footer,
All other requests are handled client side when routing in the angular app, and then the routing logic calls the specific url including ?type=json to tell the controller to respond with JSON this also avoids browser caching issues with different responses originating from the same url.
Modern frontend framework in Umbraco
Hi,
What is the experiences of using modern frontend frameworks with Umbraco? Both for backoffice and frontend? How did you integrate it? Any examples?
/Simon
On the front-end, you're free to use whatever framework you choose. With Heartcore/headless, you can go further and use whatever stack you prefer.
Backoffice is built on AngularJs, but there are examples floating around of people integrating VueJs.
Thanks for your answer. What I asked for was more like a discussion of different solutions, examples, cool tweaks and so on both for frontend and backoffice. I'm aware of that I can do the frontend however I want and that the backoffice is developed with AngularJs.
What we have done is that we use a custom controller that replaces the default MVC controller.
The controller calls a mapper we have built to generate a JSON response for the specific url.
If its an initial request we response with html including the bootstrapping code for Angular 9+ including the page json in a script tag to avoid the extra request to load the JSON, the inital request also contains json for the header and footer,
All other requests are handled client side when routing in the angular app, and then the routing logic calls the specific url including ?type=json to tell the controller to respond with JSON this also avoids browser caching issues with different responses originating from the same url.
is working on a reply...