Case Study

Five Reasons Why You Should Use a Git-Based CMS

Five Reasons Why You Should Use a Git-Based CMS

Pages 18 Pages

Traditional content management systems (CMS) are still based on architecture and technology that was introduced more than 20 years ago. To this day, the typical CMS vendor sees the primary goal of the CMS as directly enabling the business user, typically marketing. Support for developers and operations was and is a second-class concern. The whole concept of DevOps wasn’t even around when most CMS platforms were built. Today’s digital economy runs on the paradigm of Continuous Integration and Continuous Delivery (CI/CD). Where is the support for CI/CD of digital experience apps — content and code? It has been non-existent.

Join for free to read