Headless v Decoupled CMS architecture (Web CMS tries to make a comeback)

As MACH and headless Architectures are becoming the standard for modern digital experiences legacy web CMS are racing to become headless by decoupling their CMS from their opinionated frontends. Now we have decoupled and headless CMS, but is there any differences between them really?
This video helps to uncover the differences and cut through the minefield of Jargon that we are constantly bombarded with.
See more of my articles on linked in
/ jjwilliams
Most of what I have learned in the MACH / Headless world has been while building Amplience headless CMS, DAM and dynamic media services take a look here
amplience.com

[@JamesBrookeCEO]

Spot on John - you can decouple a WebCMS.. but the back-end assumptions it has around the kinds of content it's designed to manage, still apply!

[@GoingHeadlesswithJohn]

Unfortunately the term Headless really only focuses on one aspect of the new generation of CMS. As we both know its only one feature albeit an important one. The ability to free yourself from just implementing a opinionated view of the world defined 30 years ago is probably far more important and something that is overlooked by legacy CMS trying to look "headless"

[@AxxionMarketPlace-iu6ri]

Thank you