I think someone noted that at every CodeGarden since 2008, there has been at least one talk showing off Umbraco as a headless CMS. I missed which one it was this year, but you get the point.
Right now, the Umbraco website that I'm developing is completely headless with only API end points being called by an Angular and a separate Xamarin client. I don't consider what I'm doing as revolutionary.
"headless" "decoupled" architecture?
Umbraco should go "headless" "decoupled"
https://hackernoon.com/headless-vs-decoupled-cms-architecture-e240838fbc99 https://pantheon.io/decoupled-cms
Hi David,
I think someone noted that at every CodeGarden since 2008, there has been at least one talk showing off Umbraco as a headless CMS. I missed which one it was this year, but you get the point.
Right now, the Umbraco website that I'm developing is completely headless with only API end points being called by an Angular and a separate Xamarin client. I don't consider what I'm doing as revolutionary.
I mean we had it for some time;
https://our.umbraco.org/documentation/reference/routing/webapi/
and if you want to go mad, you can go headless with the backend too (If thats the right way to call it)
https://github.com/umbraco/UmbracoRestApi
Enjoy
Jonathan
Cool.
ive been through those features. if Google AMP feature is enabled it will have more performance i guess
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.