All these existing customers must be taken aboard of headless progress, to benefit from modern approaches, such as Jamstack or Experience Edge.Ģ. In all cases, the reason was "having some legacy content or modules or other dependencies, that prevent going headless". I personally have been involved in several Sitecore version upgrades, where the decision was taken to go for 10.* in containers, but without choosing a headless approach. ![]() NET Core or JSS, but also bridging legacy MVC and SXA into the world of JavaScript and JamStack. Sitecore is going to release an XM cloud in the future, so with this new feature that switch should be easier, whether you want not just. That brings the ability to incrementally convert to headless Sitecore architectures without a full rebuild, providing a bridge to new Composable DXP.
0 Comments
Leave a Reply. |