Too many bloggers pushing headless are presenting the idea that traditional CMS'es aren't also pushing forward. Traditional CMS solutions are not dying, even th

Too many bloggers pushing headless are presenting the idea that traditional CMS'es aren't also pushing forward. Traditional CMS solutions are not dying, even the infrastructure (processing and resources) are moving forward fast to improve everything as well. There is a constant industry need to change CMS and app configuration without pushing code, this is a big thing that Headless can't yet manage well without a ton of extra development work, and with that you're practically building the same solution as a CMS from scratch. There are always different use cases for each scenario/solution, and as long as vendor supplied solutions are around like ServiceNow, PowerBI & SharePoint, traditional, and especially Open-Source CMS solutions aren't going anywhere. Headless also requires a lot of work to account for unstructured data, which should, as a best practice, be fixed in your data source. Too much can slip through the test/fix gate when a bunch of customization is done to fix or re-format data at the front-end layer. Big problems occur when multiple front ends are independently displaying from one data source whenever someone tries to reformat, change, or fix data on the back-end... As a promotional practice, trust worthy company should refrain from disparaging viable alternative methods of implementation, they should stick to promotion of their own method and speak more-so to the benefits of a well thought out solution rather than saying that competing methods are "dying" IMO.